3GPP TSG RAN WG1 #120bis                        		     R1-2501827
Wuhan, China, April 7th – 11th, 2025

Source: 	vivo
Title:	Discussion on enhancement of multi-cell PUSCH/PDSCH scheduling with a single DCI
Agenda Item:	9.12.1
Document for:	Discussion and Decision

Conclusion
In this contribution, the following observations and proposals are summarized as follows: 
Proposal 1: For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1_3, follow Rel-18 operation, i.e., If the UE is not provided subslotLengthForPUCCH, the DL slot 𝑛𝐷 is the DL slot ending last, amongst the DL slots where the PDSCH receptions are scheduled by the DCI format 1_3, no RAN1 spec change is necessary.

Proposal 2: For the number of HARQ-ACK information bits for each DCI format 1_3 which is equal to M, the details of how M is implicitly derived should be clarified. Specifically,
If scheduledCellComboListDCI-1_3 is configured, apply Interpretation 1c:
Interpretation 1c: max () across all the schedulable cell combinations, where:
Number of cells for a schedulable cell combination  configured by scheduledCellComboListDCI-1-3.
 Number of HARQ-ACK bits for each scheduled cell  in the cell combination.
=0,1……-1, where  is the total number of cell combinations configured.
=0,1……-1. 
If scheduledCellComboListDCI-1_3 is not configured, apply Interpretation 1b:
Interpretation 1b: , where:
 Maximum number of HARQ-ACK bits for each scheduled cell , 
: Number of schedulable cells in a cell set.
=0,1…… .
Proposal 3: The number of HARQ-ACK bits for each serving cell is determined based on the configurations of HARQ bundling in the spatial and time domains. The logic is defined as follows:
If harq-ACK-SpatialBundlingPUCCH is configured, 
If nrofHARQ-BundlingGroups is configured, the number of HARQ-ACK bits is 
If nrofHARQ-BundlingGroups is not configured, the number of HARQ-ACK is the number of configured PDSCHs
If harq-ACK-SpatialBundlingPUCCH is not configured, 
If maxNrofCodeWordsScheduledByDCI=2 for the serving cell
If nrofHARQ-BundlingGroups is configured, the number of HARQ-ACK bits is *2
If nrofHARQ-BundlingGroups is not configured, the number of HARQ-ACK is the number of configured PDSCHs * 2
If maxNrofCodeWordsScheduledByDCI=1 for the serving cell
If nrofHARQ-BundlingGroups is configured, the number of HARQ-ACK bits is 
If nrofHARQ-BundlingGroups is not configured, the number of HARQ-ACK is the number of configured PDSCHs
Proposal 4: Confirm the working assumption:
Proposal 5: For the HARQ-ACK feedback for the invalid PDSCH due to collision with semi-static TDD DL/UL configuration, the mechanisms defined in Rel-17 and Rel-18 can be reused:
If HARQ bundling in time domain is not configured for a serving cell, the HARQ-ACK bit for an invalid PDSCH is set to NACK. 
If HARQ bundling in time domain is configured for a serving cell, Logical AND operation is applied to across all valid PDSCHs within the same bundling group to generate 1 HARQ-ACK bit per group, at least for 1-TB case.
If the group is empty or filled with only invalid PDSCH(s), HARQ-ACK bit for the bundling group is set to NACK
Proposal 6: For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs scheduled by a DCI format 1_3, the reference PDSCH is the PDSCH ending last as indicated in the DCI format 1_3 among the set of co-scheduled PDSCHs including the invalid PDSCH due to collision with uplink symbol.
Proposal 7: The candidate RRC parameters are listed in Table 3.

3GPP TSG RAN WG1 #120bis			R1- 2501885
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.12.1
Source: 	Spreadtrum, UNISOC
Title: 	Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI
Document for:	Discussion and decision

Conclusion
In this contribution, we made the following observation and proposals.
Clarify the cases of scheduling cell and scheduled cells if scheduling cell is out of set of cells, including the SCS and carrier type of scheduling cell.
Clarification for DL slot n_D in spec is needed.
SCS combinations of scheduling cell and scheduled cells affects the number of DCI.
For the same SCS and same carrier type of the scheduled cell, support at least the following cases for scheduled cells: 
Multi-cell multi-PDSCH scheduling by DCI format 1_3 is applicable to cells with 120kHz SCS  
Multi-cell multi-PUSCH scheduling by DCI format 0_3 is applicable to FR1 unlicensed TDD cells and cells with 120kHz SCS
For the different SCS and different carrier type of the scheduled cell, support at least the cases of Green box in Table 3.
Consider following options to support multi-cell multi-PUSCH/PDSCH scheduling
Rel-18 multi-PDSCH/PUSCH TDRA table is not applied to DCI format 0_1/1_1 when DCI format 0_3/1_3 is configured.
Define a new TDRA table for multi-cell multi-PUSCH/PDSCH scheduling by DCI format 0_3/1_3, and the new TDRA table and the legacy TDRA table for single-cell multi-PUSCH/PDSCH scheduling by DCI format 0_1/1_1 are not configured simultaneously.
Confirm following working assumption:
Working Assumption
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first SLIV and followed by NACK bits for the remaining SLIVs. 

3GPP TSG RAN WG1 #120bis                                                                                  R1-2501892
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.12.1
Source:	Lenovo
Title:	Discussion on multi-cell scheduling with a single DCI
Document for:	Discussion & Decision

Conclusion
In this contribution, we focus on the open issues for using a single DCI format to schedule one or multiple cells with one or multiple PUSCHs or PDSCHs per cell and have below observations and proposals:
Proposal 1: For a cell with fields repurposed for SCell dormancy indication, the corresponding MCS for TB1, the first NDI for TB1, the first RV for TB1, HARQ process number, and Antenna port(s) if antennaPortsDCI1-3= type2 is configured by higher layer, are reused for SCell dormancy indication.
Proposal 2: Adopt below TP1.

Proposal 3: For a DCI format 1_3 with fields repurposed for SCell dormancy indication and without scheduling any PDSCH, one bit of ACK is generated for SCell dormancy indication and included in the first sub-codebook regardless of the number of SLIVs indicated by the DCI format 1_3 for the cell with fields repurposed for SCell dormancy indication.
Proposal 4: Agree below TP2.

3GPP TSG RAN WG1 #120bis                                                                                       R1-2501910
Wuhan, China, 07th - 11th April 2025
Source:	ZTE Corporation, Sanechips
Title:	Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI
Agenda item:	9.12.1
Document for:	Discussion and Decision

Conclusion
Proposal 1: Consider the case involving three different SCS can be scheduled by a DCI format 0_3/1_3 in Rel-19.
Case 7: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with SCS1, TDD cell(s) with SCS2 and FR2-1 cell(s) with SCS3. 
SCS1, SCS2 and SCS3 can be same or different.
Proposal 2: For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format, there should be no spec impact.
Proposal 3: Type-1 HARQ-ACK codebook is supported for multi-cell scheduling with K1 extension for Rel-19 multi-cell scheduling.
UE expects HARQ-ACK information for all co-scheduled PDSCHs by DCI format 1_3 can be mapped in the Type-1 HARQ-ACK codebook. 
Proposal 4: Confirm the working assumption with the following updates.

Proposal 5: The maximum number of PUSCHs/PDSCHs per DCI can be configured or reported if needed.
Proposal 6: Endorse the following RRC parameters for Multi-carrier enhancements for NR Phase 3:

3GPP TSG-RAN WG1 Meeting #120bis	R1-2501960
Wuhan, China, April 7th – April 11th, 2025

Agenda Item:	9.12.1
Source:	Ericsson
Title:	Multi-cell PxSCH scheduling with a single DCI
Document for:	Discussion, Decision
1	

Conclusion
Based on the discussion in the previous sections we propose the following:
Proposal 1	Specification impact is not needed to reflect the agreement made in RAN1#120 for HARQ-ACK timing when “the UE is not provided subslotLengthForPUCCH”.
Proposal 2	Repetition and TB transmission over multiple slots (TBoMs) are not supported for the enhanced DCI 0_3/1_3.
Proposal 3	The discussion on supported scenarios should be postponed after adequate progress or competition of the feature design due to the limited TU.
Proposal 4	Case 1, Case 2 and Case 3 are supported for Rel-19 operation of DCI 0_3/1_3.
Proposal 5	Apply one of the following alternatives for configurations of the TDRA table:
	Alternative 1: Introduce a new joint TDRA table to support multi-cell multi-PxSCH scheduled by DCI format 0_3/1_3, where one or more TDRA index could be configured for each cell instead of only one TDRA index for each cell in Rel-18 and each TDRA index points to a corresponding TDRA in the TDRA table applicable for DCI format 0_1/1_1. Following the design principle of joint TDRA table in Rel-18, the following RRC parameters could be introduced:
o	tdra-FieldIndexListDCI-1-3-r19 and TDRA-FieldIndexDCI-1-3-r19
o	tdra-FieldIndexListDCI-0-3-r19 and TDRA-FieldIndexDCI-0-3-r19
	Alternative 2: Introduce new TDRA tables for support multi-cell multi-PxSCH scheduled by DCI format 0_3 and 1_3, respectively, where each TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 0_3/1_3. The following RRC parameters could be introduced:
o	MultiPDSCH-TDRA-List-r19
o	MultiPUSCH-TDRA-List-r19

3GPP TSG RAN WG1 #120bis                                           R1-2501977
Wuhan, China, April 7th – 11th, 2025

Source:         CATT
Title:            Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI
Agenda Item:    9.12.1
Document for:   Discussion and Decision

Conclusion
In this contribution, the potential spec impacts for multi-cell PUSCH/PDSCH scheduling with a single DCI are discussed. The proposals are summarized as follows:
Proposal 1: The RRC parameters for the TDRA table of DCI format 1-3/0-3 in Rel-19 can be designed as below:
Proposal 2: For the timing of PUCCH determination, there is no spec impact if the UE is not provided subslotLengthForPUCCH.
Proposal3: For supported FRs and SCSs for multi-cell multi-PUSCH/PDSCH, support at least follows: 
Multi-cell multi-PUSCH scheduling by DCI format 0_3 is applicable to FR1 and 120 kHz SCS in FR2-1.
Multi-cell multi-PDSCH scheduling by DCI format 1_3 is applicable to 120 kHz SCS in FR2-1.

3GPP TSG RAN WG1 #120bis			R1-2502034
Wuhan, China, April 7th – 11th, 2025
Agenda item:			9.12.1
Source:	China Telecom
Title:	Discussion on multi-carrier enhancements for NR phase 3
Document for:		Discussion

Conclusion
Based on the discussion in this contribution, we have following proposals:
Proposal 1: For determining the timing of a PUCCH carrying HARQ-ACK information, clarify the DL slot 𝑛𝐷 is the DL slot ending last amongst the DL slots where the more than one PDSCH are scheduled by the DCI format 1_3, if the UE is not provided subslotLengthForPUCCH, by the following TP for TS38.213:

Proposal 2: For the second sub-codebook of Rel-19 type-2 HARQ-ACK, the number of HARQ-ACK information bits for each DCI format 1_3 is equal to M, M is the maximum number of HARQ-ACK information bits which can be generated for a DCI format 1_3 across all the configured cell set(s) in the PUCCH group for the UE. For serving cell c in the co-scheduled cell combinations, 
If nrofHARQ-BundlingGroups is configured with value  and harq-ACK-SpatialBundlingPUCCH is not configured, the UE generates  HARQ-ACK bits;
If nrofHARQ-BundlingGroups is configured with value  and harq-ACK-SpatialBundlingPUCCH is configured, the UE generates  HARQ-ACK bits;
If multi-PDSCH scheduling is configured and neither nrofHARQ-BundlingGroups nor harq-ACK-SpatialBundlingPUCCH is configured, the UE generates HARQ-ACK bits;
If multi-PDSCH scheduling and harq-ACK-SpatialBundlingPUCCH are configured, and nrofHARQ-BundlingGroups is not configured, the UE generates  HARQ-ACK bits;
Where  is the value of maxNrofCodeWordsScheduledByDCI for serving cell  and  is determined by the maximum number of SLIVs corresponding to the cell amongst all rows of the joint TDRA table.
Proposal 3: Introduce new joint TDRA table tdra-FieldIndexListDCI-0-3-r19/tdra-FieldIndexListDCI-1-3-r19 to enable multiple PUSCHs/PDSCHs per scheduled cell for DCI format 0_3/1_3. The existing single-cell multi-PUSCH/PDSCH scheduling TDRA table pusch-TimeDomainAllocationListForMultiPUSCH-r16/pdsch-TimeDomainAllocationListForMultiPDSCH-r17 is applied for DCI 0_3/1_3 rather than DCI 0_1/1_1 when the new joint TDRA table is configured.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502215
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.12.1
Source:	Huawei, HiSilicon
Title:	Discussion on Rel-19 Multi-carrier enhancements
Document for:	Discussion and Decision

Conclusion
According to the above discussions, we have the following observations and proposals:
Observation 1: According to the current specification, the existing TDRA table for Rel-17 multi-PDSCH scheduling (pdsch-TimeDomainAllocationListForMultiPDSCH-r17) and Rel-16 multi-PUSCH scheduling (pusch-TimeDomainAllocationListForMultiPUSCH-r16) is not applicable for DCI format 0_3/1_3.

Proposal 1:  Support new TDRA tables for each scheduled cell to enable multi-PxSCH scheduling of DCI format 0_3/1_3. These TDRA tables can follow the same structure as the legacy TDRA tables used for multi-PxSCH scheduling of DCI format 0_1/1_1.

Proposal 2: Support new joint TDRA tables for DCI format 0_3/1_3 in Rel-19 MCE.
tdra-FieldIndexListDCI-1-3-r19 and tdra-FieldIndexListDCI-0-3-r19.

Proposal 3: Support to increase the TDRA field size in DCI format 0_3/1_3 for Rel-19 MCE.

Proposal 4: For the slot-based PUCCH, the definition of the DL slot  impacts the RAN1 specification.
Adopt the above proposed TP.

Proposal 5: Confirm the above Working Assumption.

3GPP TSG RAN WG1 #120bis	                                                            	 R1-2502282
Wuhan, China, April 7th – 11st, 2025

Source:	OPPO
Title:	Discussion of multi-cell scheduling with a single DCI
Agenda Item:	9.12.1
Document for:	Discussion and Decision

Conclusions
In this contribution, we discuss the enhancements to multi-cell PUSCH/PDSCH scheduling with a single DCI with following observations and proposals:
Proposal 1: For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1_3 when UE is not provided subslotLengthForPUCCH, the DL slot  in the spec is clarified as following:

Proposal 2: Whether to support multi-PDSCH scheduling per scheduled cell by DCI format 1_3 in FR1 should be discussed.
Proposal 3: The following two options can be considered for the TDRA table applicable for multi-PUSCH/PDSCH scheduling by DCI format 0_3/1_3:
Option 1: Reuse the legacy TDRA table for multi-PUSCH/PDSCH scheduling by DCI format 0_1/1_1, and specify additional configuration/indication to determine the applicable DCI format when the legacy TDRA table is configured.
Option 2: Define new TDRA tables for multi-PUSCH/PDSCH scheduling by DCI format 0_3/1_3, and the new TDRA table and the legacy TDRA table for multi-PUSCH/PDSCH scheduling by DCI format 0_1/1_1 are not configured simultaneously.

3GPP TSG RAN WG1 #120bis	 R1-2502388
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.12.1
Source:	Samsung
Title:	Enhancements for multi-cell PUSCH/PDSCH scheduling
Document for:	Discussion and decision

Conclusions
This contribution considered the Rel-19 enhancements for multi-cell scheduling of PUSCHs/PDSCHs using DCI format 0_3/1_3 and provided the following proposals.
Proposal 1: For the FFS from RAN1#120 meeting, no additional specification is needed for determination of PUCCH timing for Rel-19 multi-cell scheduling with different SCS.
If the UE is not provided subslotLengthForPUCCH, the DL slot 𝑛𝐷 is the DL slot ending last, amongst the DL slots where the PDSCH receptions are scheduled by the DCI format 1_3.
FFS: No RAN1 spec impact
Proposal 2: Discuss whether to update the field type of the ‘minimum scheduling offset indicator’ field (e.g., from Type-1A to Type-1B).
Proposal 3: For RRC configuration of the TDRA table for DCI format 0_3/1_3 with multi-PxSCH scheduling:
The Rel-19 TDRA table follows the structure of Rel-18 TDRA table (e.g., tdra-FieldIndexList-1-3) to provide a list of multi-cell TDRA combinations;
Support increasing the number of multi-cell TDRA combinations (e.g., 64 for DL, 128 for UL);
Each multi-cell TDRA combination follows the structure of Rel-18 TDRA combinations (e.g., TDRA-FieldIndexDCI-1-3) to provide TDRA entries per BWP per cell;
Each TDRA entry is an integer (e.g., integer (0.. maxNrofDL-Allocation[Ext])) that points to an entry (e.g., MultiPDSCH-TDRA) from a list of multi-PxSCH TDRA combinations (e.g., multiPDSCH-TDRA-List) for the corresponding BWP/Cell.
Proposal 4: For TDRA field in DCI format 0_3/1_3 with multi-PUSCH/PDSCH scheduling:
Clarify that “the TDRA table applicable for multi-PUSCH/PDSCH scheduling by DCI format 0_3/1_3 for the corresponding cell” does not apply to DCI formats 0_1/1_1.
Proposal 5: For the number of bits of NDI/RV fields in DCI format 0_3/1_3 with multi-PUSCH/PDSCH scheduling:
Conclude that the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell is determined by TDRA table for the active BWP of the cell.
Proposal 6: For determining the number M of HARQ-ACK information bits for each DCI format 1_3 corresponding to the second HARQ-ACK sub-codebook in a PUCCH transmission:
M is a maximum over all the configured cell set(s) S in a PUCCH group of the sum of  (if nrofHARQ-BundlingGroups is not provided for a serving cell c) or  (if nrofHARQ-BundlingGroups is provided for the serving cell c) across serving cells c of a respective cell set S that can be co-scheduled by a DCI format 1_3;
 is the maximum number of SLIVs amongst all rows of the multi-PDSCH TDRA table configured on the active BWP of the serving cell c;
 is the maximum number of transport block groups (TBGs) for first TBs (and for second TBs, if configured) for the serving cell c if harq-ACKSpatialBundlingPUCCH is not provided, or the maximum number of PDSCH reception groups on the serving cell c if harq-ACKSpatialBundlingPUCCH is provided, and is provided by RRC parameter nrofHARQ-BundlingGroups;
 is the value of maxNrofCodeWordsScheduledByDCI for serving cell c when harq-ACKSpatialBundlingPUCCH is not provided; otherwise ;
No further optimization based on the multi-cell TDRA table.
Proposal 7: For determination of the number of HARQ-ACK bits for PUCCH power control, reuse the Rel-18 MCE formula with the following modifications:
 is the number M of HARQ-ACK information bits per DCI format 1_3, as per Proposal 6;
 is based on the number of TB / PDSCH receptions when nrofHARQ-BundlingGroups is not configured, or the number of transport block groups (TBGs) or PDSCH groups when nrofHARQ-BundlingGroups is configured.
Proposal 8: An SCell dormancy indication by repurposing fields of DCI format 1_3 corresponding to a cell:
does not mandate the TDRA field to indicate a row with a single SLIV for a corresponding serving cell;
follows the Rel-17 design to use the entire NDI and RV fields (including one or multiple NDI/RV blocks corresponding to one or multiple PDSCH SLIVs indicated by the TDRA field) of such serving cell for SCell dormancy indication – no RAN1 spec impact;
is assumed as one successful PDSCH reception on the corresponding cell, and corresponds to one ACK – additional padding NACKs are same as for any other DCI format 1_3 as per Proposal 6:
Confirm the WA from RAN1#120 with the addition of “no RAN1 spec impact”.
Working Assumption (RAN1#120)
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first SLIV and followed by NACK bits for the remaining SLIVs.
No RAN1 spec impact


References:
RP-242408, New WID: Multi-carrier enhancements for NR Phase 2, RAN#105, Lenovo.
R1-2501377, Feature lead summary #4 on multi-cell scheduling with a single DCI, RAN1#120, Moderator (Lenovo).

3GPP TSG RAN WG1 #120bis			                 R1-2502484
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.12.1
Source: 	LG Electronics
Title: 	Discussion on single DCI based multi-cell scheduling for Rel-19
Document for:	Discussion and decision

Conclusions
In this contribution, we discussed remaining issues on the single DCI based multi-cell PDSCH/PUSCH scheduling for Rel-19, and the following proposals are provided:

Proposal #1: No RAN1 spec impact is needed for the agreement on the determination of HARQ-ACK transmission timing for a set of co-scheduled PDSCHs by a DCI format 1_3.

Proposal #2: Confirm the working assumption on the HARQ-ACK mapping for Scell dormancy indication by DCI format 1_3 scheduling one or more PDSCHs. 

3GPP TSG RAN WG1 #120bis		R1-2502493
Wuhan, China, April 7th – 11th, 2025

Source:	Panasonic
Title: 	Discussion on multi-carrier enhancements for NR Phase 3
Agenda Item:		9.12.1
Document for:	Discussion

Conclusion
In this contribution, we provide our view on multi-carrier enhancements for NR Phase 3. We made following proposals.
Proposal 1: No specification change is essential on the determination of the DL slot  for the scenario having multiple PDSCHs with different SCSs. If clarification is necessary, consider the following change to TS 38.213 Section 9.2.3.
Proposal 2: Separate multi-PxSCH TDRA table configuration for multi-cell multi-PxSCH scheduling using DCI format 0-3/1-3 is configured.
Proposal 3: Whether repetition and/or TBoMS is supported for Rel.19 DCI format 0-3/1-3 should be decided.

3GPP TSG RAN WG1 #120bis	R1-2502495
Wuhan, China, April 7th – 11th, 2025

	
Agenda item:		9.12.1
Source:	Nokia
Title:	Remaining details on Rel-19 Multi-carrier enhancements
Document for:		Discussion and Decision

Conclusions 
In this contribution we discuss the remaining issues on R19 multi-cell scheduling enhancements with a single DCI. 
The discussions on remaining open issues in Sec. 2 can be summarized in the following related observations and proposals: 
Observation 2.1: The current specifications for Rel-17 (for multi-PDSCH scheduling) and Rel-18 (for multi-cell scheduling) seem to be ambiguous in terms of defining the UL slot n for the HARQ-ACK timing / transmission in slot n +k , as the multiple PDSCHs scheduling by a DCI format are only considered in the determination of k (i.e. k1) and not determination of the UL slot n.  
Observation 2.2: As the ‘ending’ in the current specifications seem to refer to the ending of the one or more PDSCH receptions (and not the associated slot), specification changes for the mixed SCS operation and slot-based PUCCH seem to be needed. 
Proposal 2.1: Discuss if the following clarification is necessary or if the specification can be considered sufficiently clear without it


The discussions on RRC parameters in Sec. 3 can be summarized in the following related observations and proposals: 
Observation 3.1: The existing TDRA tables for R17 multi-PDSCH and R16 multi-PUSCH scheduling (i.e. pdsch-TimeDomainAllocationListForMultiPDSCH and pusch-TimeDomainAllocationListForMultiPUSCH) cannot be directly re-used for MC scheduling using DCI formats 0_3/1_3, as these tables automatically configure/enable the multi-PxSCH operation for DCI formats 0_1/1_1.  
Proposal 3.1: Support new configurable TDRA tables per scheduled cell for multi-PxSCH scheduling of DCI format 0_3/1_3 having the same structure and size as the existing configurable TDRA tables for multi-PxSCH of DCI formats 0_1/1_1.
e.g. pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 and pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3 to differentiate from pdsch-TimeDomainAllocationListForMultiPDSCH-r17 and pusch-TimeDomainAllocationListForMultiPUSCH-r16.

Proposal 3.2: Support a maximum TDRA field size of 8 bits (i.e. max. ITDRA=256) in DCI format 0_3/1_3
Observation 3.2: The Rel-18 TDRA field index lists for DCI formats 0_3/1_3 (i.e. tdra-FieldIndexListDCI-0-3-r18 / tdra-FieldIndexListDCI-1-3-r18) cannot be reused for the combined operation with multi-PxSCH scheduling as (i) the number of scheduling combinations is less than the number of TDRA entries possible for a single cell and (ii) the max. number of DL allocations for a scheduled cell is limited to 16 (and not 64, as for multi-PDSCH scheduling). 
Proposal 3.3: Support new TDRA field index lists for DCI format 0_3/1_3 to (i) account for the needed increased scheduling flexibility for multi-PxSCH scheduling and (ii) to allow addressing larger underlying DL BWP specific TDRA tables for multi-PDSCH scheduling. 

Resulting in the following proposed RRC parameter list: 

3GPP TSG RAN WG1 #120bis                                                                                                R1-2502574
Wuhan, China, April 7th – 11th, 2025

Source:               TCL
Title:                    Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI
Agenda item:      9.12.1
Document for:    Discussion and Decision

Conclusion
In this contribution, the following proposal has been made:
Proposal 1: For the reference PDSCH for HARQ-ACK reporting when co-scheduled PDSCH with different SCS by a single DCI, the following clarification is needed. 








4. 

3GPP TSG RAN WG1 #120bis	R1- 2502720
Wuhan, China, 7th – 11th April, 2025

Agenda item:		9.12.1
Source:	MediaTek Inc.
Title:	Multi-carrier enhancements for NR Phase 3 
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 commercial 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: Limit multi-PxSCH scheduling to 120kHz SCS. Limit scheduling cell SCS to be always lower than scheduled cell SCS for multi-PxSCH scheduling.
Proposal 3: Consider whether to limit also multi-PUSCH across slots to FR2 cells.
Proposal 4: Total co-scheduled PxSCHs by MC-DCI across all cells shall not exceed 16.
Proposal 5: For the MC-DCI structure, ensure that DCI fields containing information required to receive the 1st slot for all co-scheduled cells is not interleaved with the fields containing slot-specific information for subsequent slots of the same cells.

3GPP TSG RAN WG1 #120bis                                                                                             R1-2502783
Wuhan, CN, April 7th – 11st, 2025

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

Conclusion 
In this contribution, we made following observations, proposals and proposed conclusion.

Observation 1: The current spec can cover the scenario having multiple PDSCHs with different SCSs.
If the UE is not provided subslotLengthForPUCCH,  is the last UL slot for PUCCH transmission that overlaps with the DL slot  in which the PDSCH/PDCCH reception(s) is/are ending, regardless of SCS.
Observation 2: If all possible cases are supported and arbitrary combination of SCSs/carrier types is allowed, UE capability design would be very complex, and long discussion would be required.
Observation 3: Rel-18 RAN1 specifications on DCI format 1_3/0_3 would be applicable to the case with different SCS/carrier type among co-scheduled cells.
Observation 4: According to WID, when UE is configured with multi-cell multi-PUSCH/PDSCH scheduling, “TDRA table applicable for DCI format 1_1” which is referred by the joint TDRA table entries (TDRA-FieldIndexDCI-1-3-r18 or TDRA-FieldIndexDCI-0-3-r18) cannot be TDRA table for multi-PUSCH/PDSCH scheduling.

Proposal 1: Following agreement should be updated with deletion of FFS.
For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1_3, follow Rel-18 operation.
If the UE is not provided subslotLengthForPUCCH, the DL slot 𝑛𝐷 is the DL slot ending last, amongst the DL slots where the more than one PDSCH are scheduled by the DCI format 1_3.
FFS: RAN1 spec impact till RAN1#120-bis
If the UE is provided subslotLengthForPUCCH, no spec change is necessary.
Note: Specification of this feature shall not impact the existing UE processing PDSCH timeline requirement for any individual PDSCH, as specified in 5.3.1 of TS38.214.
Proposal 2: Simple capability structure is preferable and should be discussed in UE feature discussion.
Proposal 3: Specification impacts to support different SCS/carrier type among co-scheduled cells include at least followings.
updating TS38.300 to remove the restriction
introducing new UE capability(es) for the support of different SCS/carrier type among co-scheduled cells
Proposal 4: Separate new TDRA table for multi-PUSCH/PDSCH scheduling for each BWP of each cell to be referred by the joint TDRA table needs to be introduced.
New joint TDRA tables and entries like tdra-FieldIndexListDCI-1-3-r18, tdra-FieldIndexListDCI-0-3-r18, TDRA-FieldIndexDCI-1-3-r18 and TDRA-FieldIndexDCI-0-3-r18 are necessary to refer separate new TDRA table for multi-PUSCH/PDSCH scheduling for each BWP of each cell instead of “TDRA table applicable for DCI format 1_1”.
Separate new TDRA tables for multi-PUSCH/PDSCH scheduling for each BWP of each cell from PUSCH-TimeDomainResourceAllocationList-r16 and MultiPDSCH-TDRA-List-r17 are necessary to be used for multi-cell multi-PDSCH/PUSCH scheduling via DCI format 1_3/0_3 instead of “single-cell multi-PDSCH/PUSCH scheduling via DCI format 1_1/0_1”.

Proposed conclusion 1: All bits in the reserved fields corresponding to the cell with smallest serving cell index with invalid FDRA can be used for SCell dormancy indication case 2, and no spec change is necessary.

3GPP TSG RAN WG1 Meeting #120bis    	            R1-2502859
Wuhan, China, April 7th – 11th, 2025

Source:	Qualcomm Incorporated
Title:	Multi-cell PUSCH/PDSCH scheduling with a single DCI
Agenda Item:	9.12.1
Document for: 	Discussion and Decision

Conclusion
In this contribution, we share our views on Rel-19 multi-cell PDSCH/PUSCH scheduling with a single DCI provided following proposals.

Proposal 1:
Adopt the following change in TS38.213 to reflect the RAN1 agreement.

Proposal 2:
Consider following RRC configuration for TDRA table for multi-cell multi-PDSCH scheduling by a DCI.
tdra-FieldIndexListDCI-1-3-r19 SEQUENCE (SIZE (1..32)) OF TDRA-FieldIndexDCI-1-3-r19
TDRA-FieldIndexDCI-1-3-r19 ::= SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r19)) OF MultiPDSCH-TDRA-r19
MultiPDSCH-TDRA-r19            SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs-r19)) OF INTEGER (0 ..maxNrofDL-Allocations-1-r18)

Proposal 3:
Consider following RRC configuration for TDRA table for multi-cell multi-PUSCH scheduling by a DCI.
tdra-FieldIndexListDCI-0-3-r19 SEQUENCE (SIZE (1..64)) OF TDRA-FieldIndexDCI-0-3-r19
TDRA-FieldIndexDCI-0-3-r19 ::= SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r19)) OF MultiPUSCH-TDRA-r19
MultiPUSCH-TDRA-r19            SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r19)) OF INTEGER (0 ..maxNrofUL-Allocations-1-r19)
maxNrofUL-Allocations-1-r19 INTEGER ::= 63

Proposal 4:
If RRC signalling reduction method for TDRA table for multi-cell multi-PxSCH scheduling is desirable, consider bundling BWPs for different cells with the same SCS as a single column as follows
maxNrofSCSBWPsInSetOfCells-r19 denotes the summation across cells of the maximum number of BWPs having different SCSs
BWPs with the same SCS across cells are bundled into a single column of the TDRA table
tdra-FieldIndexListDCI-1-3-r19 SEQUENCE (SIZE (1..32)) OF TDRA-FieldIndexDCI-1-3-r19
TDRA-FieldIndexDCI-1-3-r19 ::= SEQUENCE (SIZE (2.. maxNrofSCSBWPsInSetOfCells-r19)) OF MultiPDSCH-TDRA-r19
MultiPDSCH-TDRA-r19            SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs-r19)) OF INTEGER (0 ..maxNrofDL-Allocations-1-r18)

3GPP TSG RAN WG1 #120bis	R1- 2502998
Wuhan, China, 7th – 11th April, 2025

Agenda item:		9.12.1
Source:	MediaTek Inc.
Title:	Multi-carrier enhancements for NR Phase 3 
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 commercial 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: Limit multi-PDSCH scheduling across slots to 120kHz SCS FR2-1 scheduled cells. Consider whether to limit also multi-PUSCH across slots to FR2-1 scheduled cells.
Proposal 3: Limit scheduling cell SCS to be always lower than scheduled cell SCS for multi-PxSCH scheduling.
Proposal 4: Total co-scheduled PxSCHs by MC-DCI across all cells shall not exceed 16.
Proposal 5: For the MC-DCI structure, ensure that DCI fields containing information required to receive the 1st slot for all co-scheduled cells is not interleaved with the fields containing slot-specific information for subsequent slots of the same cells.

3GPP TSG RAN WG1 Meeting #120bis	                         R1-2503037
Wuhan, China, April 7th – 11th, 2025

Source:                Moderator (Lenovo)
Title:                     Feature lead summary #1 on multi-cell scheduling with a single DCI
Agenda item:       9.12.1
Document for:     Discussion and Decision

Conclusion
For a cell scheduled by DCI format 0_3/1_3 with valid FDRA value, UE does not expect that a Type-1B field in the DCI format indicates a code point that does not correspond to a configuration for the cell.
No RAN1 spec impact


Agreements made in RAN1#117

Agreement
The TP in draft CR R1-2404235 for TS38.212 on correcting precoding information and number of layers in DCI format 0_3 is agreed for alignment CR. Editor to submit CR.

Agreement
The TP in draft CR R1-2404856 for TS38.212 on correcting number of MCS/NDI/RV blocks for TB-2 in DCI 1_3 is agreed for alignment CR. Editor to submit CR.

Agreement
Following TP is agreed for TS38.214. Final in CR in R1-2405734.
5.1.5	Antenna ports quasi co-location

When tci-PresentInDCI is set as 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET, a UE configured with dl-OrJointTCI-StateList with activated TCI-State or ul-TCI-StateList with activated TCI-UL-State receives DCI format 1_1/1_2/1_3 providing indicated TCI-State(s) and/or TCI-UL-State(s) for a CC or all CCs in the same CC list configured by simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2-r17, simultaneousU-TCI-UpdateList3-r17, simultaneousU-TCI-UpdateList4-r17. The DCI format 1_1/1_2 can be with or without, if applicable, DL assignment. If the DCI format 1_1/1_2 is without DL assignment, the UE can assume the following:
-	CS-RNTI is used to scramble the CRC for the DCI
-	The values of the following DCI fields are set as follows:
-	RV = all '1's
-	MCS = all '1's
-	NDI = 0
-	Set to all '0's for FDRA Type 0, or all '1's for FDRA Type 1, or all '0's for dynamicSwitch (same as in Table 10.2-4 of [6, TS 38.213]). 
After a UE receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State and before application of an indicated TCI state from the configured TCI states:
-	The UE assumes that DM-RS of PDSCH and DM-RS of PDCCH and the CSI-RS applying the indicated TCI state are quasi co-located with the SS/PBCH block the UE identified during the initial access procedure
*** Unchanged parts are omitted ***

Agreement
The TP in R1-2404855 for TS38.212 on correcting Type-2 field blocks in DCI 1_3/0_3 is agreed but without the addition of “counted towards ”, “counted towards ”. The TP is agreed for alignment CR.



Agreements made in RAN1#118
Agreement
When a PDCCH MO that provides a DCI format 1_3 is before an active DL BWP change on a cell of co-scheduled cells by the DCI format 1_3, and the active DL BWP change for the cell is not triggered in the PDCCH MO, and the PUCCH indicated by the DCI format 1_3 starts at or after a slot for the active DL BWP change on the cell,
For Type 1 codebook and for Type 2 codebook for generating the first sub-codebook, follow the legacy behaviour (the corresponding HARQ-ACK information for that scheduled cell with active DL BWP change is skipped)
No spec impact
For Type 2 codebook for generating the second sub-codebook, 
the HARQ-ACK information for that scheduled cell with active DL BWP change is generated with NACK bit.

Agreement
The TP in draft CR R1-2405930 for TS38.214 on corrections of DCI format 0_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406796 for TS38.213 on corrections of UCI-onPUSCH for DCI format 0_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406620 for TS38.213 on correcting search space for DCI format 0_3/1_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2407164 for TS38.212 on correcting table caption for DCI format 0_3/1_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406339 for TS38.213 on correcting Type-2 HARQ-ACK codebook determination is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406341 for TS38.213 on correcting Type-2 HARQ-ACK codebook determination is agreed as alignment CR.


Agreement
Adopt the following TP for Section 10.1, TS38.213 on PDCCH overbooking is agreed in principle for alignment.

10.1 UE procedure for determining physical downlink control channel assignment 
< Unchanged parts are omitted >
For all search space sets that a UE monitors PDCCH on the primary cell within a slot , or within a group of  slots for a corresponding combination , or within a span in slot , denote by  a set of CSS sets, except for CSS sets provided by searchSpaceMCCH, searchSpaceMTCH or by SearchSpace in pdcch-ConfigMulticast for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, with cardinality of  and by  a set of USS sets and CSS sets provided by searchSpaceMCCH, searchSpaceMTCH or by SearchSpace in pdcch-ConfigMulticast for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI with cardinality of  for scheduling on the primary cell with PDCCH candidates and non-overlapping CCEs counted on the primary cell. The location of search space sets , , in  is according to an ascending order of the search space set index.
< Unchanged parts are omitted >

Agreement
Adopt the following TP for Section 9.1.5, TS38.213 is agreed in principle for alignment.
< Unchanged parts are omitted >
9.1.5	HARQ-ACK codebook retransmission 
With reference to slots of PUCCH transmissions on the primary cell and for Type-1 or Type-2 HARQ-ACK codebooks, a UE that transmitted or would transmit a PUCCH or a PUSCH with a first HARQ-ACK codebook in slot  can be indicated by a DCI format with CRC scrambled by a C-RNTI or a MCS-C-RNTI that does not schedule a PDSCH reception [4, TS 38.212] on one or more serving cells and is received in a PDCCH ending in slot , to transmit a PUCCH with the first HARQ-ACK codebook in slot , where slot  is after slot . The UE determines  and a resource for the PUCCH transmission as described in clauses 9.2.3 and 9.2.5. If the UE is provided a periodic cell switching pattern for PUCCH transmissions by pucch-sSCellPattern, the UE further determines a corresponding cell based on the periodic cell switching pattern as described in clause 9.A.
If the HARQ-ACK retransmission indicator field value in a DCI format is '1', the UE determines slot  as  where  is determined by a one-to-one mapping in ascending order among the values from -7 to 24 and the values of 
-	the MCS field for transport block 1 if the DCI format is DCI format 1_1 
-	the MCS field if the DCI format is DCI format 1_2 
-	the MCS field for transport block 1 for a serving cell if the DCI format is DCI format 1_3, where the serving cell is the one with smallest index that has 
-	resourceAllocation = resourceAllocationType0 and all bits of the corresponding block of the frequency domain resource assignment field equal to 0, or
-	resourceAllocation = resourceAllocationType1 and all bits of the corresponding block of the frequency domain resource assignment field equal to 1, or
-	resourceAllocation = dynamicSwitch and all bits of the corresponding block of the frequency domain resource assignment field equal to 0 or 1
If the DCI format includes a priority indicator field having a value, a priority value of first HARQ-ACK information in the first HARQ-ACK codebook is same as the value of the priority indicator field; otherwise, the priority value of the first HARQ-ACK information is zero.
< Unchanged parts are omitted >
Agreement
Adopt the following TP for Section 5.1.5, Rel-18 TS38.214 is agreed in principle for alignment.

5.1.5	Antenna ports quasi co-location

When a UE configured with dl-OrJointTCI-StateList would transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to the DCI carrying the TCI State indication and without DL assignment, or corresponding to the one or more PDSCHs scheduled by the DCI carrying the TCI State indication, and if the indicated TCI State(s) is/are different from the previously indicated one(s), the indicated TCI-State(s) and/or TCI-UL-State(s) should be applied starting from the first slot that is at least  symbols after the last symbol of the PUCCH or the PUSCH, and if the UE receives more than one indicated TCI state for a CC/BWP to be applied starting from the first slot that is at least  symbols after the last symbol of the PUCCH or the PUSCH, the indicated TCI state carried in the latest DCI, for the corresponding coresetPoolIndex value when applicable, in time corresponding to positive HARQ-ACK value is applied. The first slot and the  symbols are both determined on the active BWP with the smallest SCS among the BWP(s) from the CCs applying the indicated TCI-State(s) or TCI-UL-State(s) that are active at the end of the PUCCH or the PUSCH carrying the positive HARQ-ACK. 


Agreement
Draft CR in Section 11 of R1-2407227 is endorsed in principle.

Agreement
Final CR R1-247545 is endorsed.

Agreements made in RAN1#118bis
For Rel-18 CR
Agreement
Adopt the following TP for Section 6.1.2.2, TS38.214 in principle for alignment CR.

6.1.2.2	Resource allocation in frequency domain
-------------------------------------Begin of TP----------------------------------------------
The UE shall determine the resource block assignment in frequency domain using the resource allocation field in the detected PDCCH DCI except for a PUSCH transmission scheduled by a RAR UL grant or fallbackRAR UL grant, in which case the frequency domain resource allocation is determined according to clause 8.3 of [6, 38.213] or a MsgA PUSCH transmission with frequency domain resource allocation determined according to clause 8.1A of [6, 38.213]. Three uplink resource allocation schemes type 0, type 1 and type 2 are supported. Uplink resource allocation scheme type 0 is supported for PUSCH only when transform precoding is disabled. Uplink resource allocation scheme type 1 and type 2 are supported for PUSCH for both cases when transform precoding is enabled or disabled.
If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the 'Frequency domain resource' assignment field by setting a higher layer parameter resourceAllocation in pusch-Config to 'dynamicSwitch', for DCI format 0_1 or setting a higher layer parameter resourceAllocationDCI-0-2 in pusch-Config to 'dynamicSwitch' for DCI format 0_2 or setting a higher layer parameter resourceAllocationDCI-0-3 in pusch-ConfigDCI-0-3 to 'dynamicSwitch' for DCI format 0_3, the UE shall use uplink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter resourceAllocation for DCI format 0_1 or the higher layer parameter resourceAllocationDCI-0-2 for DCI format 0_2. The UE shall assume that when the scheduling PDCCH is received with DCI format 0_1  and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, uplink type 2 resource allocation is used.
-------------------------------------End of TP----------------------------------------------
Agreement
Adopt the TP in R1-2408629 for Section 7.3.1.1.4, TS38.212 in principle for alignment CR with additional change of the changed text “mapped” to “associated”.

Agreement
Adopt the following TP for Section 12, TS38.213 in principle for alignment CR.

12	Bandwidth part operation 
< Unchanged parts are omitted >
The UE does not expect to be scheduled by a DCI format 1_3 to receive a PDSCH on an activated SCell, if:
-	the DCI format 1_3 indicates an active DL BWP provided by dormantBWP-Id for the activated SCell, and
-	resourceAllocation = resourceAllocationType0 and not all bits of a block of the frequency domain resource assignment field associated with the activated SCell in the DCI format 1_3 are equal to 0, or
-	resourceAllocation = resourceAllocationType1 and not all bits of a block of the frequency domain resource assignment field associated with the activated SCell in the DCI format 1_3 are equal to 1, or
-	resourceAllocation = dynamicSwitch and not all bits of a block of the frequency domain resource assignment field associated with the activated SCell in the DCI format 1_3 are equal to either 0 or 1
 of the blockare 
< Unchanged parts are omitted >

Agreement
Draft CR R1-2408973 to TS38.214 is endorsed in principle for alignment CR.

Agreement
Adopt the following TP for Section 5.1.5, TS38.214 in principle for alignment CR.

5.1.5	Antenna ports quasi co-location
< Unchanged parts are omitted >
When a UE supports two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' the UE may receive an activation command, as described in clause 6.1.3.24 of [10, TS 38.321], the activation command is used to map up to 8 combinations of one or two TCI states to the codepoints of the DCI field 'Transmission Configuration Indication'. The UE is not expected to receive more than 8 TCI states in the activation command. 

When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and when the number of codepoints S in the DCI field 'Transmission Configuration Indication' of DCI format 1_2 is smaller than the number of TCI codepoints that are activated by the activation command, as described in clause 6.1.3.14, 6.1.3.24 and 6.1.3.47 of [10, TS38.321], only the first S activated codepoints are applied for DCI format 1_2. 
< Unchanged parts are omitted >


For Rel-19 MCE:

Agreement
For multiple PUSCHs/PDSCHs scheduled on a cell by a DCI format 0_3/1_3, 
Common FDRA is applied to the PUSCHs/PDSCHs on the cell as Rel-16/17 multi-PUSCH/PDSCH scheduling.
Common MCS is applied to the PUSCHs/PDSCHs on the cell as Rel-16/17 multi-PUSCH/PDSCH scheduling.
HARQ process number indicated for the cell is applied to the first scheduled PUSCH/PDSCH and then incremented by 1 for subsequent PUSCHs/PDSCHs on the cell (with modulo operation if needed) as Rel-16/17 multi-PUSCH/PDSCH scheduling.

Agreement
In DCI format 0_3/1_3, for each block of NDI field, consider the following options:
Option 1: the number of bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3.
Option 2: the number of bits is equal to the actual number of scheduled PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3. 
Option 3: if the number of scheduled PUSCH/PDSCH is 1, then one bit NDI is applied; otherwise, option 1 is applied. 

Agreement
In DCI format 0_3/1_3, for each block of RV field, consider the following options:
Option 1: the number of bits is determined based on the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured for the corresponding cell.
Option 2: the number of bits is determined based on the actual number of scheduled PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured for the corresponding cell.
Option 3: if the number of scheduled PUSCH/PDSCH is 1, then option 2 is applied; otherwise, option 1 is applied.

Agreement
A single TDRA field in DCI format 0_3/1_3 indicates one row from a joint TDRA table. 
Each row in the table contains only one TDRA index for each BWP of each cell within the set of cells. Each TDRA index points to one or multiple time domain resource allocations in the TDRA table applicable for multi-PUSCH/PDSCH scheduling by DCI format 0_3/1_3 for the corresponding cell.

Agreement
Time domain HARQ-ACK bundling is supported.

Agreement
Consider at least the case that up to two different SCS can be scheduled by a DCI format 0_3/1_3 in Rel-19.
Consider at least the following cases for scheduled cells in Rel-19: 
Case 1: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with SCS1 and FR1 licensed TDD cell(s) with SCS2.
SCS1 can be same or different to SCS2.
Case 2: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2. 
SCS1 can be same or different to SCS2.
Case 3: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed TDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2. 
SCS1 can be same or different to SCS2.
Case 4: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with different SCS.
Case 5: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed TDD cell(s) with different SCS.
Case 6: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR2-1 cell(s) with different SCS. 




Agreements made in RAN1#119
For Rel-18 CR:
Agreement
Draft CR R1-2410190 to TS 38.213 is endorsed in principle as alignment CR.

Agreement
Draft CR R1-2410598 to TS 38.212 is endorsed in principle as alignment CR.

Agreement
Draft CR R1-2409665 to TS 38.213 is endorsed in principle as alignment CR.

Agreement
Draft CR R1-2410897 to TS 38.213 is endorsed in principle as alignment CR.


For Rel-19 MCE:

Agreement
Time-domain HARQ-ACK bundling is configured per cell as Rel-17.  

Agreement
Specification supports the maximum number of PUSCHs/PDSCHs for a scheduled cell by a DCI format 0_3/1_3 is 8.
Payload size of a DCI format 0_3/1_3 exceeding 140 is not supported in Rel-19.

Agreement
Type-2 HARQ-ACK codebook is generated by concatenating a first sub-codebook and a second sub-codebook. 
The first sub-codebook comprises HARQ-ACK information bits for PDSCH(s) scheduled by DCI(s) with each scheduling a single PDSCH, or each scheduling a single cell with multiple PDSCHs on it and nrofHARQ-BundlingGroups configured as 1, and HARQ-ACK information bit(s) for DCI(s) having associated HARQ-ACK information without scheduling PDSCH reception. 
The second sub-codebook comprises HARQ-ACK information bits for PDSCHs scheduled by DCI(s) with each scheduling more than one cell, or each scheduling a single cell with multiple PDSCHs on it without nrofHARQ-BundlingGroups or nrofHARQ-BundlingGroups configured larger than 1. 
Separate DAI counting is applied for DCI(s) associated with the first sub-codebook and DCI(s) associated with the second sub-codebook as Rel-18.
Note: For providing HARQ-ACK information corresponding to SCell dormancy indication, the UE assumes that the UE receives a PDSCH on the serving cell associated with fields in DCI format 1_3 used for SCell dormancy indication as Rel-18.         


Agreement
For the second sub-codebook, the number of HARQ-ACK information bits for each DCI format 1_3 is equal to M, to select one of the following options.
Option 1: M is the maximum number of HARQ-ACK information bits which can be generated for a DCI format 1_3 across all the configured cell set(s) in the PUCCH group for the UE. M is implicitly derived based on RRC configuration. 
Option 2: M is explicitly configured by RRC parameter for the PUCCH group.
Other options are not precluded.

Agreement
For NDI indication in DCI format 0_3/1_3 for TB1, further study
Option 1: For each block of NDI field, the number of bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3.
Maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell is determined by TDRA table for the cell.
Option 2a: Total number of bits of the NDI field is equal to the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
The number of bits of a block of NDI field corresponding to a scheduled cell is equal to the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 on the cell.
Some reserved bits are needed when the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 is smaller than the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
Other options are not precluded.
Note: For Option 1 and 2a, DCI format 0_3/1_3 has  blocks of NDI field for TB1, same as in Rel-18.

Agreement
For RV indication in DCI format 0_3/1_3 for TB1, further study
Option 1: For each block of RV field, the number of bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured for the cell.
Maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell is determined by TDRA table for the cell.
Option 2a: Total number of bits of the RV field is determined based on the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
The number of bits of a block of RV field corresponding to a scheduled cell is determined based on the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 on the cell and number of bits for RV configured for the cell.
Some reserved bits are needed when the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 is smaller than the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
Other options are not precluded.
Note: For Option 1 and 2a, DCI format 0_3/1_3 has  blocks of RV field for TB1, same as in Rel-18.

Agreements made in RAN1#120
Agreement
For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1_3, follow Rel-18 operation.
If the UE is not provided subslotLengthForPUCCH, the DL slot 𝑛𝐷 is the DL slot ending last, amongst the DL slots where the more than one PDSCH are scheduled by the DCI format 1_3.
FFS: RAN1 spec impact till RAN1#120-bis
If the UE is provided subslotLengthForPUCCH, no spec change is necessary.
Note: Specification of this feature shall not impact the existing UE processing PDSCH timeline requirement for any individual PDSCH, as specified in 5.3.1 of TS38.214.

Agreement
For the second sub-codebook, the number of HARQ-ACK information bits for each DCI format 1_3 is equal to M.
M is the maximum number of HARQ-ACK information bits which can be generated for a DCI format 1_3 across all the configured cell set(s) in the PUCCH group for the UE. M is implicitly derived based on RRC configuration. 

Agreement
For NDI indication in DCI format 0_3/1_3 for a TB,
Option 1 is adopted.

Agreement
For RV indication in DCI format 0_3/1_3 for a TB,
Option 1 is adopted.

Agreement
For multi-PUSCH/PDSCH scheduling using a DCI format 0_3/1_3, 1 bit RV indication is determined according to Table 7.3.1.2.3-1 of TS 38.212.
Note: This is aligned with Rel-18 DCI format 0_3/1_3 for cells configured with 1 bit RV by numberOfBitsForRV-DCI-0-3/1-3.   

Agreement
For the second sub-codebook, the HARQ-ACK information bits for a DCI format 1_3 are ordered firstly according to same ordering as in Rel-17 multi-PDSCHs scheduling for PDSCH receptions on a same serving cell, then according to ascending order of associated serving cell indexes.

Agreement
For Type-1C fields in DCI format 0_3, when the TDRA field indicates more than one scheduled PUSCHs on the scheduled cell with the smallest cell index:
The CSI request field applies to the PUSCH determined based on Rel-17 multi-PUSCH scheduling on same serving cell. 
Note for background: When the TDRA field of DCI format 0_3 indicates only one scheduled PUSCH on the scheduled cell with the smallest cell index, DCI interpretation and UE procedure is same as in Rel-18.

Working Assumption
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first SLIV and followed by NACK bits for the remaining SLIVs.

Agreement
Regarding presence of UL-SCH field, 
1 bit UL-SCH field is always present in DCI format 0_3.
UL-SCH field and CSI request field in a DCI format 0_3 are applied to the same PUSCH.

Agreement
For NDI/RV indication in DCI format 0_3/1_3 for a TB, 
Within each block of NDI field, the NDI bits are placed in the LSBs based on the SLIV position in the indicated TDRA row. Padding bits, if any, are placed in the MSBs within the block.
Within each block of RV field, the RV bits are placed in the LSBs based on the SLIV position in the indicated TDRA row. Padding bits, if any, are placed in the MSBs within the block.

3GPP TSG RAN WG1 Meeting #120bis	                         R1-2503038
Wuhan, China, April 7th – 11th, 2025

Source:                Moderator (Lenovo)
Title:                     Feature lead summary #2 on multi-cell scheduling with a single DCI
Agenda item:       9.12.1
Document for:     Discussion and Decision

Conclusion
For a cell scheduled by DCI format 0_3/1_3 with valid FDRA value, UE does not expect that a Type-1B field in the DCI format indicates a code point that does not correspond to a configuration for the cell.
No RAN1 spec impact


Agreements made in RAN1#117

Agreement
The TP in draft CR R1-2404235 for TS38.212 on correcting precoding information and number of layers in DCI format 0_3 is agreed for alignment CR. Editor to submit CR.

Agreement
The TP in draft CR R1-2404856 for TS38.212 on correcting number of MCS/NDI/RV blocks for TB-2 in DCI 1_3 is agreed for alignment CR. Editor to submit CR.

Agreement
Following TP is agreed for TS38.214. Final in CR in R1-2405734.
5.1.5	Antenna ports quasi co-location

When tci-PresentInDCI is set as 'enabled' or tci-PresentDCI-1-2 is configured for the CORESET, a UE configured with dl-OrJointTCI-StateList with activated TCI-State or ul-TCI-StateList with activated TCI-UL-State receives DCI format 1_1/1_2/1_3 providing indicated TCI-State(s) and/or TCI-UL-State(s) for a CC or all CCs in the same CC list configured by simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2-r17, simultaneousU-TCI-UpdateList3-r17, simultaneousU-TCI-UpdateList4-r17. The DCI format 1_1/1_2 can be with or without, if applicable, DL assignment. If the DCI format 1_1/1_2 is without DL assignment, the UE can assume the following:
-	CS-RNTI is used to scramble the CRC for the DCI
-	The values of the following DCI fields are set as follows:
-	RV = all '1's
-	MCS = all '1's
-	NDI = 0
-	Set to all '0's for FDRA Type 0, or all '1's for FDRA Type 1, or all '0's for dynamicSwitch (same as in Table 10.2-4 of [6, TS 38.213]). 
After a UE receives an initial higher layer configuration of dl-OrJointTCI-StateList with more than one TCI-State and before application of an indicated TCI state from the configured TCI states:
-	The UE assumes that DM-RS of PDSCH and DM-RS of PDCCH and the CSI-RS applying the indicated TCI state are quasi co-located with the SS/PBCH block the UE identified during the initial access procedure
*** Unchanged parts are omitted ***

Agreement
The TP in R1-2404855 for TS38.212 on correcting Type-2 field blocks in DCI 1_3/0_3 is agreed but without the addition of “counted towards ”, “counted towards ”. The TP is agreed for alignment CR.



Agreements made in RAN1#118
Agreement
When a PDCCH MO that provides a DCI format 1_3 is before an active DL BWP change on a cell of co-scheduled cells by the DCI format 1_3, and the active DL BWP change for the cell is not triggered in the PDCCH MO, and the PUCCH indicated by the DCI format 1_3 starts at or after a slot for the active DL BWP change on the cell,
For Type 1 codebook and for Type 2 codebook for generating the first sub-codebook, follow the legacy behaviour (the corresponding HARQ-ACK information for that scheduled cell with active DL BWP change is skipped)
No spec impact
For Type 2 codebook for generating the second sub-codebook, 
the HARQ-ACK information for that scheduled cell with active DL BWP change is generated with NACK bit.

Agreement
The TP in draft CR R1-2405930 for TS38.214 on corrections of DCI format 0_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406796 for TS38.213 on corrections of UCI-onPUSCH for DCI format 0_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406620 for TS38.213 on correcting search space for DCI format 0_3/1_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2407164 for TS38.212 on correcting table caption for DCI format 0_3/1_3 is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406339 for TS38.213 on correcting Type-2 HARQ-ACK codebook determination is agreed as alignment CR.

Agreement
The TP in draft CR R1-2406341 for TS38.213 on correcting Type-2 HARQ-ACK codebook determination is agreed as alignment CR.


Agreement
Adopt the following TP for Section 10.1, TS38.213 on PDCCH overbooking is agreed in principle for alignment.

10.1 UE procedure for determining physical downlink control channel assignment 
< Unchanged parts are omitted >
For all search space sets that a UE monitors PDCCH on the primary cell within a slot , or within a group of  slots for a corresponding combination , or within a span in slot , denote by  a set of CSS sets, except for CSS sets provided by searchSpaceMCCH, searchSpaceMTCH or by SearchSpace in pdcch-ConfigMulticast for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, with cardinality of  and by  a set of USS sets and CSS sets provided by searchSpaceMCCH, searchSpaceMTCH or by SearchSpace in pdcch-ConfigMulticast for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI with cardinality of  for scheduling on the primary cell with PDCCH candidates and non-overlapping CCEs counted on the primary cell. The location of search space sets , , in  is according to an ascending order of the search space set index.
< Unchanged parts are omitted >

Agreement
Adopt the following TP for Section 9.1.5, TS38.213 is agreed in principle for alignment.
< Unchanged parts are omitted >
9.1.5	HARQ-ACK codebook retransmission 
With reference to slots of PUCCH transmissions on the primary cell and for Type-1 or Type-2 HARQ-ACK codebooks, a UE that transmitted or would transmit a PUCCH or a PUSCH with a first HARQ-ACK codebook in slot  can be indicated by a DCI format with CRC scrambled by a C-RNTI or a MCS-C-RNTI that does not schedule a PDSCH reception [4, TS 38.212] on one or more serving cells and is received in a PDCCH ending in slot , to transmit a PUCCH with the first HARQ-ACK codebook in slot , where slot  is after slot . The UE determines  and a resource for the PUCCH transmission as described in clauses 9.2.3 and 9.2.5. If the UE is provided a periodic cell switching pattern for PUCCH transmissions by pucch-sSCellPattern, the UE further determines a corresponding cell based on the periodic cell switching pattern as described in clause 9.A.
If the HARQ-ACK retransmission indicator field value in a DCI format is '1', the UE determines slot  as  where  is determined by a one-to-one mapping in ascending order among the values from -7 to 24 and the values of 
-	the MCS field for transport block 1 if the DCI format is DCI format 1_1 
-	the MCS field if the DCI format is DCI format 1_2 
-	the MCS field for transport block 1 for a serving cell if the DCI format is DCI format 1_3, where the serving cell is the one with smallest index that has 
-	resourceAllocation = resourceAllocationType0 and all bits of the corresponding block of the frequency domain resource assignment field equal to 0, or
-	resourceAllocation = resourceAllocationType1 and all bits of the corresponding block of the frequency domain resource assignment field equal to 1, or
-	resourceAllocation = dynamicSwitch and all bits of the corresponding block of the frequency domain resource assignment field equal to 0 or 1
If the DCI format includes a priority indicator field having a value, a priority value of first HARQ-ACK information in the first HARQ-ACK codebook is same as the value of the priority indicator field; otherwise, the priority value of the first HARQ-ACK information is zero.
< Unchanged parts are omitted >
Agreement
Adopt the following TP for Section 5.1.5, Rel-18 TS38.214 is agreed in principle for alignment.

5.1.5	Antenna ports quasi co-location

When a UE configured with dl-OrJointTCI-StateList would transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to the DCI carrying the TCI State indication and without DL assignment, or corresponding to the one or more PDSCHs scheduled by the DCI carrying the TCI State indication, and if the indicated TCI State(s) is/are different from the previously indicated one(s), the indicated TCI-State(s) and/or TCI-UL-State(s) should be applied starting from the first slot that is at least  symbols after the last symbol of the PUCCH or the PUSCH, and if the UE receives more than one indicated TCI state for a CC/BWP to be applied starting from the first slot that is at least  symbols after the last symbol of the PUCCH or the PUSCH, the indicated TCI state carried in the latest DCI, for the corresponding coresetPoolIndex value when applicable, in time corresponding to positive HARQ-ACK value is applied. The first slot and the  symbols are both determined on the active BWP with the smallest SCS among the BWP(s) from the CCs applying the indicated TCI-State(s) or TCI-UL-State(s) that are active at the end of the PUCCH or the PUSCH carrying the positive HARQ-ACK. 


Agreement
Draft CR in Section 11 of R1-2407227 is endorsed in principle.

Agreement
Final CR R1-247545 is endorsed.

Agreements made in RAN1#118bis
For Rel-18 CR
Agreement
Adopt the following TP for Section 6.1.2.2, TS38.214 in principle for alignment CR.

6.1.2.2	Resource allocation in frequency domain
-------------------------------------Begin of TP----------------------------------------------
The UE shall determine the resource block assignment in frequency domain using the resource allocation field in the detected PDCCH DCI except for a PUSCH transmission scheduled by a RAR UL grant or fallbackRAR UL grant, in which case the frequency domain resource allocation is determined according to clause 8.3 of [6, 38.213] or a MsgA PUSCH transmission with frequency domain resource allocation determined according to clause 8.1A of [6, 38.213]. Three uplink resource allocation schemes type 0, type 1 and type 2 are supported. Uplink resource allocation scheme type 0 is supported for PUSCH only when transform precoding is disabled. Uplink resource allocation scheme type 1 and type 2 are supported for PUSCH for both cases when transform precoding is enabled or disabled.
If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the 'Frequency domain resource' assignment field by setting a higher layer parameter resourceAllocation in pusch-Config to 'dynamicSwitch', for DCI format 0_1 or setting a higher layer parameter resourceAllocationDCI-0-2 in pusch-Config to 'dynamicSwitch' for DCI format 0_2 or setting a higher layer parameter resourceAllocationDCI-0-3 in pusch-ConfigDCI-0-3 to 'dynamicSwitch' for DCI format 0_3, the UE shall use uplink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter resourceAllocation for DCI format 0_1 or the higher layer parameter resourceAllocationDCI-0-2 for DCI format 0_2. The UE shall assume that when the scheduling PDCCH is received with DCI format 0_1  and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, uplink type 2 resource allocation is used.
-------------------------------------End of TP----------------------------------------------
Agreement
Adopt the TP in R1-2408629 for Section 7.3.1.1.4, TS38.212 in principle for alignment CR with additional change of the changed text “mapped” to “associated”.

Agreement
Adopt the following TP for Section 12, TS38.213 in principle for alignment CR.

12	Bandwidth part operation 
< Unchanged parts are omitted >
The UE does not expect to be scheduled by a DCI format 1_3 to receive a PDSCH on an activated SCell, if:
-	the DCI format 1_3 indicates an active DL BWP provided by dormantBWP-Id for the activated SCell, and
-	resourceAllocation = resourceAllocationType0 and not all bits of a block of the frequency domain resource assignment field associated with the activated SCell in the DCI format 1_3 are equal to 0, or
-	resourceAllocation = resourceAllocationType1 and not all bits of a block of the frequency domain resource assignment field associated with the activated SCell in the DCI format 1_3 are equal to 1, or
-	resourceAllocation = dynamicSwitch and not all bits of a block of the frequency domain resource assignment field associated with the activated SCell in the DCI format 1_3 are equal to either 0 or 1
 of the blockare 
< Unchanged parts are omitted >

Agreement
Draft CR R1-2408973 to TS38.214 is endorsed in principle for alignment CR.

Agreement
Adopt the following TP for Section 5.1.5, TS38.214 in principle for alignment CR.

5.1.5	Antenna ports quasi co-location
< Unchanged parts are omitted >
When a UE supports two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' the UE may receive an activation command, as described in clause 6.1.3.24 of [10, TS 38.321], the activation command is used to map up to 8 combinations of one or two TCI states to the codepoints of the DCI field 'Transmission Configuration Indication'. The UE is not expected to receive more than 8 TCI states in the activation command. 

When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and when the number of codepoints S in the DCI field 'Transmission Configuration Indication' of DCI format 1_2 is smaller than the number of TCI codepoints that are activated by the activation command, as described in clause 6.1.3.14, 6.1.3.24 and 6.1.3.47 of [10, TS38.321], only the first S activated codepoints are applied for DCI format 1_2. 
< Unchanged parts are omitted >


For Rel-19 MCE:

Agreement
For multiple PUSCHs/PDSCHs scheduled on a cell by a DCI format 0_3/1_3, 
Common FDRA is applied to the PUSCHs/PDSCHs on the cell as Rel-16/17 multi-PUSCH/PDSCH scheduling.
Common MCS is applied to the PUSCHs/PDSCHs on the cell as Rel-16/17 multi-PUSCH/PDSCH scheduling.
HARQ process number indicated for the cell is applied to the first scheduled PUSCH/PDSCH and then incremented by 1 for subsequent PUSCHs/PDSCHs on the cell (with modulo operation if needed) as Rel-16/17 multi-PUSCH/PDSCH scheduling.

Agreement
In DCI format 0_3/1_3, for each block of NDI field, consider the following options:
Option 1: the number of bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3.
Option 2: the number of bits is equal to the actual number of scheduled PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3. 
Option 3: if the number of scheduled PUSCH/PDSCH is 1, then one bit NDI is applied; otherwise, option 1 is applied. 

Agreement
In DCI format 0_3/1_3, for each block of RV field, consider the following options:
Option 1: the number of bits is determined based on the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured for the corresponding cell.
Option 2: the number of bits is determined based on the actual number of scheduled PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured for the corresponding cell.
Option 3: if the number of scheduled PUSCH/PDSCH is 1, then option 2 is applied; otherwise, option 1 is applied.

Agreement
A single TDRA field in DCI format 0_3/1_3 indicates one row from a joint TDRA table. 
Each row in the table contains only one TDRA index for each BWP of each cell within the set of cells. Each TDRA index points to one or multiple time domain resource allocations in the TDRA table applicable for multi-PUSCH/PDSCH scheduling by DCI format 0_3/1_3 for the corresponding cell.

Agreement
Time domain HARQ-ACK bundling is supported.

Agreement
Consider at least the case that up to two different SCS can be scheduled by a DCI format 0_3/1_3 in Rel-19.
Consider at least the following cases for scheduled cells in Rel-19: 
Case 1: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with SCS1 and FR1 licensed TDD cell(s) with SCS2.
SCS1 can be same or different to SCS2.
Case 2: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2. 
SCS1 can be same or different to SCS2.
Case 3: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed TDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2. 
SCS1 can be same or different to SCS2.
Case 4: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with different SCS.
Case 5: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed TDD cell(s) with different SCS.
Case 6: A DCI format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR2-1 cell(s) with different SCS. 




Agreements made in RAN1#119
For Rel-18 CR:
Agreement
Draft CR R1-2410190 to TS 38.213 is endorsed in principle as alignment CR.

Agreement
Draft CR R1-2410598 to TS 38.212 is endorsed in principle as alignment CR.

Agreement
Draft CR R1-2409665 to TS 38.213 is endorsed in principle as alignment CR.

Agreement
Draft CR R1-2410897 to TS 38.213 is endorsed in principle as alignment CR.


For Rel-19 MCE:

Agreement
Time-domain HARQ-ACK bundling is configured per cell as Rel-17.  

Agreement
Specification supports the maximum number of PUSCHs/PDSCHs for a scheduled cell by a DCI format 0_3/1_3 is 8.
Payload size of a DCI format 0_3/1_3 exceeding 140 is not supported in Rel-19.

Agreement
Type-2 HARQ-ACK codebook is generated by concatenating a first sub-codebook and a second sub-codebook. 
The first sub-codebook comprises HARQ-ACK information bits for PDSCH(s) scheduled by DCI(s) with each scheduling a single PDSCH, or each scheduling a single cell with multiple PDSCHs on it and nrofHARQ-BundlingGroups configured as 1, and HARQ-ACK information bit(s) for DCI(s) having associated HARQ-ACK information without scheduling PDSCH reception. 
The second sub-codebook comprises HARQ-ACK information bits for PDSCHs scheduled by DCI(s) with each scheduling more than one cell, or each scheduling a single cell with multiple PDSCHs on it without nrofHARQ-BundlingGroups or nrofHARQ-BundlingGroups configured larger than 1. 
Separate DAI counting is applied for DCI(s) associated with the first sub-codebook and DCI(s) associated with the second sub-codebook as Rel-18.
Note: For providing HARQ-ACK information corresponding to SCell dormancy indication, the UE assumes that the UE receives a PDSCH on the serving cell associated with fields in DCI format 1_3 used for SCell dormancy indication as Rel-18.         


Agreement
For the second sub-codebook, the number of HARQ-ACK information bits for each DCI format 1_3 is equal to M, to select one of the following options.
Option 1: M is the maximum number of HARQ-ACK information bits which can be generated for a DCI format 1_3 across all the configured cell set(s) in the PUCCH group for the UE. M is implicitly derived based on RRC configuration. 
Option 2: M is explicitly configured by RRC parameter for the PUCCH group.
Other options are not precluded.

Agreement
For NDI indication in DCI format 0_3/1_3 for TB1, further study
Option 1: For each block of NDI field, the number of bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3.
Maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell is determined by TDRA table for the cell.
Option 2a: Total number of bits of the NDI field is equal to the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
The number of bits of a block of NDI field corresponding to a scheduled cell is equal to the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 on the cell.
Some reserved bits are needed when the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 is smaller than the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
Other options are not precluded.
Note: For Option 1 and 2a, DCI format 0_3/1_3 has  blocks of NDI field for TB1, same as in Rel-18.

Agreement
For RV indication in DCI format 0_3/1_3 for TB1, further study
Option 1: For each block of RV field, the number of bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured for the cell.
Maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell is determined by TDRA table for the cell.
Option 2a: Total number of bits of the RV field is determined based on the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
The number of bits of a block of RV field corresponding to a scheduled cell is determined based on the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 on the cell and number of bits for RV configured for the cell.
Some reserved bits are needed when the actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3 is smaller than the maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the co-schedulable cells.
Other options are not precluded.
Note: For Option 1 and 2a, DCI format 0_3/1_3 has  blocks of RV field for TB1, same as in Rel-18.

Agreements made in RAN1#120
Agreement
For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1_3, follow Rel-18 operation.
If the UE is not provided subslotLengthForPUCCH, the DL slot 𝑛𝐷 is the DL slot ending last, amongst the DL slots where the more than one PDSCH are scheduled by the DCI format 1_3.
FFS: RAN1 spec impact till RAN1#120-bis
If the UE is provided subslotLengthForPUCCH, no spec change is necessary.
Note: Specification of this feature shall not impact the existing UE processing PDSCH timeline requirement for any individual PDSCH, as specified in 5.3.1 of TS38.214.

Agreement
For the second sub-codebook, the number of HARQ-ACK information bits for each DCI format 1_3 is equal to M.
M is the maximum number of HARQ-ACK information bits which can be generated for a DCI format 1_3 across all the configured cell set(s) in the PUCCH group for the UE. M is implicitly derived based on RRC configuration. 

Agreement
For NDI indication in DCI format 0_3/1_3 for a TB,
Option 1 is adopted.

Agreement
For RV indication in DCI format 0_3/1_3 for a TB,
Option 1 is adopted.

Agreement
For multi-PUSCH/PDSCH scheduling using a DCI format 0_3/1_3, 1 bit RV indication is determined according to Table 7.3.1.2.3-1 of TS 38.212.
Note: This is aligned with Rel-18 DCI format 0_3/1_3 for cells configured with 1 bit RV by numberOfBitsForRV-DCI-0-3/1-3.   

Agreement
For the second sub-codebook, the HARQ-ACK information bits for a DCI format 1_3 are ordered firstly according to same ordering as in Rel-17 multi-PDSCHs scheduling for PDSCH receptions on a same serving cell, then according to ascending order of associated serving cell indexes.

Agreement
For Type-1C fields in DCI format 0_3, when the TDRA field indicates more than one scheduled PUSCHs on the scheduled cell with the smallest cell index:
The CSI request field applies to the PUSCH determined based on Rel-17 multi-PUSCH scheduling on same serving cell. 
Note for background: When the TDRA field of DCI format 0_3 indicates only one scheduled PUSCH on the scheduled cell with the smallest cell index, DCI interpretation and UE procedure is same as in Rel-18.

Working Assumption
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first SLIV and followed by NACK bits for the remaining SLIVs.

Agreement
Regarding presence of UL-SCH field, 
1 bit UL-SCH field is always present in DCI format 0_3.
UL-SCH field and CSI request field in a DCI format 0_3 are applied to the same PUSCH.

Agreement
For NDI/RV indication in DCI format 0_3/1_3 for a TB, 
Within each block of NDI field, the NDI bits are placed in the LSBs based on the SLIV position in the indicated TDRA row. Padding bits, if any, are placed in the MSBs within the block.
Within each block of RV field, the RV bits are placed in the LSBs based on the SLIV position in the indicated TDRA row. Padding bits, if any, are placed in the MSBs within the block.

3GPP TSG RAN WG1 Meeting #120bis	                         R1-2503039
Wuhan, China, April 7th – 11th, 2025

Source:                Moderator (Lenovo)
Title:                     Feature lead summary #3 on multi-cell scheduling with a single DCI
Agenda item:       9.12.1
Document for:     Discussion and Decision

Conclusion
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and without scheduling any PDSCH, one bit of ACK is generated for SCell dormancy indication and included in the first sub-codebook regardless of the number of SLIVs indicated by the DCI format 1_3 for the cell with fields repurposed for SCell dormancy indication.

Agreement
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA and nrofHARQ-BundlingGroups is not provided for the serving cell, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first SLIV and followed by NACK bits for the remaining SLIVs. 
For a DCI format 1_3 with fields repurposed for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with smallest serving cell index with invalid FDRA and nrofHARQ-BundlingGroups is provided for the serving cell, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first TBG, and followed by NACK bits for the remaining TBGs, if any.
Note: Related working assumption made in RAN1#120 meeting does not need to be confirmed.

Agreement
For determining the number M of HARQ-ACK information bits for each DCI format 1_3 corresponding to the second HARQ-ACK sub-codebook in a PUCCH transmission:
M is a maximum number over all the configured cell set(s) S in a PUCCH group of the sum of  (if nrofHARQ-BundlingGroups is not provided for a serving cell c) or  (if nrofHARQ-BundlingGroups is provided for the serving cell c) across serving cells of a respective cell set S that can be co-scheduled by a DCI format 1_3;
 is the maximum number of SLIVs amongst all rows of the multi-PDSCH TDRA table configured on the active BWP of the serving cell c;
 is the maximum number of transport block groups (TBGs) for first TBs (and for second TBs, if configured) for the serving cell c if harq-ACKSpatialBundlingPUCCH is not provided, or the maximum number of PDSCH reception groups on the serving cell c if harq-ACKSpatialBundlingPUCCH is provided, and is provided by RRC parameter nrofHARQ-BundlingGroups;
 is the value of maxNrofCodeWordsScheduledByDCI for serving cell c when harq-ACKSpatialBundlingPUCCH is not provided; otherwise .