| R1-2503271.docx |
|---|
3GPP TSG-RAN WG1 Meeting #121 R1-2503271 St Julian’s, Malta, May 19th – 23rd, 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: Proposal 1: At least Case 1, Case 2 and Case 3 are supported for Rel-19 multi-carrier enhancement. Proposal 2: Support co-scheduled cells with up to three SCSs being scheduled by DCI format 0_3/1_3 in Rel-19. Proposal 3: Support to increase the maximum number of rows in joint TDRA table for DCI format 1_3/0_3 in Rel-19 MCE. - the maximum number of rows can be set to 64 for TDRA-FieldIndexListDCI-1-3-r19. - the maximum number of rows can be set to 128 for TDRA-FieldIndexListDCI-0-3-r19. Proposal 4: TB processing over multiple slots (TBoMS) is not supported for Rel-19 DCI format 0_3. Proposal 5: Defer the discussion of PUCCH power control issue for Rel-19 MCE to maintenance phase, till that for Rel-18 MCE is resolved. |
| R1-2503330 Discussion on multi-cell PUSCHPDSCH scheduling with a single DCI.docx |
3GPP TSG RAN WG1 #121 R1-2503330 St Julian’s, Malta, May 19th – 23rd, 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: 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 3: For multi-cell multi-PDSCH scheduling, if the active DL BWP change occurs on one scheduled cell and the HARQ-ACK information bits are included in the second sub-codebook of Type-2 codebook, the UE assumes incorrect decoding for transport blocks in each of the PDSCH receptions scheduled by the DCI format 1_3 on the scheduled cell. Proposal 4: RAN1 should clarify how to put the padding bits for multi-cell multi-PDSCH scheduling. Understanding 1: The padding bits are added at the end of HARQ information bits for the DCI format 1_3. Understanding 2: The padding bits are added per scheduled cell. Proposal 5: The maximum number of PUSCHs/PDSCHs per DCI can be configured or reported if needed. Proposal 6: Endorse the following updates on RRC parameters for Multi-carrier enhancements for NR Phase 3: |
| R1-2503383 Remaining issues on enhancement of multi-cell PUSCH and PDSCH scheduling with a single DCI.docx |
3GPP TSG RAN WG1 #121 R1-2503383 St Julian’s, Malta, May 19th – 23rd, 2025 Source: vivo Title: Remaining issues 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 proposal is as follows: Proposal 1: “the first SLIV” in the RAN1#120bis agreement should be clarified as “the SLIV with the earliest starting time”. Proposal 2: The TP1 for TS 38213 is adopted. ----------------------------------------------------Start of TP1 of TS 38213------------------------------------------------- 9.1.3.1 Type-2 HARQ-ACK codebook in physical uplink control channel *** Unchanged parts are omitted *** - the second HARQ-ACK sub-codebook is associated with DCI format 1_3 that - schedules PDSCH receptions on more than one serving cells from the set of serving cells, or - schedules more than one PDSCH receptions on a serving cell , from the set of serving cells, for which the UE is not provided nrofHARQ-BundlingGroups or is provided nrofHARQ-BundlingGroups with value , or - does not include a SCell dormancy indication field or the SCell dormancy indication field is reserved, indicates SCell dormancy, and schedules PDSCH receptions on one or more serving cells from the set of serving cells - in the above, and for the purpose of providing HARQ-ACK information corresponding to SCell dormancy indication by the DCI format 1_3 - the UE assumes that the UE receives one PDSCH, with earliest starting time among one or more PDSCH receptions scheduled by first SLIV in the row of pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 for DCI format 1_3, on the serving cell associated with fields in DCI format 1_3 for SCell dormancy indication, as described in Clause 10.3, and that the PDSCH provides one transport block that the UE correctly decodes, if the UE is not provided nrofHARQ-BundlingGroups for the serving cell - the UE assumes that the UE receives one or more PDSCHs associated with a TBG with smallest index, or a PDSCH reception group with smallest index, among one or more PDSCH receptions scheduled by the DCI format 1_3, on the serving cell associated with fields in DCI format 1_3 for SCell dormancy indication, as described in Clause 10.3, and that each of the one or more PDSCHs provides one transport block that the UE correctly decodes if the UE is provided nrofHARQ-BundlingGroups for the serving cell - the UE assumes incorrect decoding for transport blocks in each of the remaining PDSCH receptions scheduled by the DCI format 1_3 on the serving cell associated with fields in DCI format 1_3 for SCell dormancy indication ----------------------------------------------------End of TP1 of TS 38213----------------------------------------------------- Proposal 3: The maximum number of rows of both TDRA-FieldIndexListDCI-1-3-r19 and TDRA-FieldIndexListDCI-0-3-r19 are 64. |
| R1-2503429 MC_enh Phase 3.docx |
3GPP TSG RAN WG1 #121 R1- 2503429 St Julian, Malta, 19 – 23 May 2025 Agenda item: 9.12.1 Source: Nokia Title: Remaining details on Rel-19 Multi-carrier enhancements WI code: NR_MC_enh2 Release: Rel-19 Document for: Discussion and Decision |
Conclusion In this contribution we discuss the remaining details on R19 MC-enhancements phase 4 and make the following observations proposals: Proposal 1: Agree the following TP to TS 38.300 Sec. 10.11: Observation 1: Increased flexibility of up to 256 entries in TDRA-FieldIndexListDCI-0-3/1-3 is required for the gNB to jointly indicate the intended number of PDSCHs/PUSCHs and their time-domain location for a co-scheduled cell for multi-cell scheduling. Observation 2: The impact of up to 256 entries in TDRA-FieldIndexListDCI-0-3/1-3 to the DCI size seems negligible and is under gNB control by RRC configuration. The required UE memory of up to 256 entries is only a fraction (a small single digit percentage) compared to the underlying BWP specific multi-PDSCH/multi-PUSCH TDRA tables for DCI format 0_3/1_3. Proposal 2: Support up to 256 entries for TDRA-FieldIndexListDCI-0-3/1-3 to provide the required flexibility for the gNB to jointly indicate the intended number of PDSCHs/PUSCHs and their time-domain location for a co-scheduled cell for multi-cell scheduling. Proposal 3: Adopt the TP to 38.213 on clarifying UL slot for multi-PDSCH HARQ reporting of Alt. 3 of the moderator proposal 3-1 of RAN1#120bis which reads as: |
| R1-2503587-R19MCE-May-2025-v1 - clean.docx |
3GPP TSG RAN WG1 #121 R1-2503587 Malta, MT, May 19th – 23rd, 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: Update the field type of the ‘minimum scheduling offset indicator’ field from Type-1A to Type-1B. Proposal 2: To resolve the FFS on the range of RRC parameters TDRA-FieldIndexListDCI-1-3-r19 and TDRA-FieldIndexListDCI-0-3-r19: support increasing the number of multi-cell TDRA combinations, e.g., 64 for DL and 128 for UL, to ensure same flexibility as in Rel-18. Proposal 3: For the number of bits of NDI/RV fields in DCI format 0_3/1_3 with multi-PUSCH/PDSCH scheduling: the maximum number of schedulable PUSCHs/PDSCHs on the corresponding cell is determined by TDRA table for the active BWP of the cell. Proposal 4: For the application of FG 18-9 (type2-HARQ-ACK-Codebook) to Rel-19 multi-cell multi-PDSCH scheduling: The UE counts a serving cell a number times in the Type-2 HARQ-ACK pseudo-code, when the UE receives DCI formats 1_3 in the same PDCCH MO that schedule PDSCH receptions, with , and the serving cell is a serving cell with smallest cell index across the DCI formats; Adopt TP #1 in the Appendix for TS 38.213. Proposal 5: 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 of HARQ-ACK information bits per DCI format 1_3, as per draft CR for TS 38.213 [5, R1-2503173]; 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 reception groups when nrofHARQ-BundlingGroups is configured, along with legacy handling for overlap with UL symbols of the TDD UL/DL configuration; Adopt one of TP #2A or TP #2B in the Appendix for TS 38.213. Proposal 6: Further clarification of the per-cell number of HARQ-ACK information bits, e.g., as part of the “modifications” to the pseudo-code for the Rel-19 MCE is not necessary – such text already exists in the endorsed draft CR for TS 38.213 [5, R1-2503173]. Appendix: Suggested TPs TP #1 for Proposal 4 (against TS 38.213 v18.6.0) // Application of FG 18-9 to multi-cell multi-PDSCH scheduling *** Unchanged parts are omitted *** The UE determines the , for a total number of HARQ-ACK information bits in the second Type-2 HARQ-ACK sub-codebook according to the following pseudo-code. Set to the maximum number of serving cells in ScheduledCell-ListDCI-1-3 of a set of serving cells provided by MC-DCI-SetofCells, across the number of sets of serving cells, that can be scheduled PDSCH receptions by DCI format 1_3 Set to the maximum total number of TBs in PDSCH receptions that can be scheduled by a DCI format 1_3 over more than one serving cells in a set of serving cells across the number of sets of serving cells Set to the number of sets of serving cells MC-DCI-SetofCells in a PUCCH group Set to the number of serving cells, across sets of serving cells in the PUCCH group Set to the index of serving cells, , a lower index corresponds to a lower RRC index of a corresponding serving cell - if the UE indicates type2-HARQ-ACK-Codebook and receives PDSCHs on a serving cell that are scheduled by DCI formats 1_3, where , in PDCCH receptions at a same PDCCH monitoring occasion , where - each of the DCI formats 1_3 schedules more than one PDSCH receptions on respective more than one serving cells, - is the smallest cell index among the respective more than one serving cells that are scheduled by each of the DCI formats 1_3, and - is same across the DCI formats 1_3 the serving cell is counted times for PDCCH monitoring occasion in increasing order of the respective earliest PDSCH reception starting time, for each of the DCI formats 1_3, among the PDSCH receptions Set to the index of a serving cell, in a set of indexes of serving cells arranged in ascending order, from the set of serving cells, *** Unchanged parts are omitted *** TP #2A for Proposal 5 (against the endorsed draft CR [5, R1-2503173]) // PUCCH power control with multi-cell multi-PDSCH scheduling – Alt-1: as part of the “modifications” for Rel-19 MCE if harq-ACK-SpatialBundlingPUCCH is not provided, else end if for any . If and , and a UE is not provided pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 for any serving cell in a PUCCH group, or provided nrofHARQ-BundlingGroups with value of 1 for any serving cell that is provided pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3, or for PDSCH receptions scheduled by a DCI format 1_3 that does not schedule more than one PDSCH reception on each serving cell, or for PDSCH receptions scheduled by a DCI format 1_3 on a serving cell when the UE is provided nrofHARQ-BundlingGroups with value of 1 for obtaining a PUCCH transmission power as described in clause 7.2.1, the UE determines , where is the value of for the first Type-2 HARQ-ACK sub-codebook and is the value of for the second Type-2 HARQ-ACK sub-codebook that is determined as where - in the following - a DCI format 1_3 schedules more than one PDSCH receptions providing transport blocks with enabled HARQ-ACK information - a dormancy indication is considered as a PDSCH reception providing a single transport block with enabled HARQ-ACK information - is the value of the total DAI field in a last DCI format 1_3 the UE detects in a last PDCCH monitoring occasion within the PDCCH monitoring occasions where the UE detects at least one DCI format 1_3. if the UE does not detect any DCI format 1_3 in any of the PDCCH monitoring occasions. - is the total number of DCI format 1_3 that the UE detects within the PDCCH monitoring occasions for the set of serving cells. if the UE does not detect any DCI format 1_3 associated with scheduling on set of serving cells in any of the PDCCH monitoring occasions. - if harq-ACK-SpatialBundlingPUCCH is not provided; otherwise, . - is - the number of transport blocks, in PDSCH receptions not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is not provided - the number of more than one PDSCHs, not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, scheduled by a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is provided If a UE is provided pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 for a serving cell in a set of serving cells provided by MC-DCI-SetofCells in a PUCCH group, the UE determines the according to the previous pseudo-codes with the following modifications - the first HARQ-ACK sub-codebook is associated with - unicast SPS PDSCH receptions - any unicast DCI format scheduling a single PDSCH reception on a serving cell - any unicast DCI format having associated HARQ-ACK information without scheduling a PDSCH reception - any DCI format 1_3 scheduling more than one PDSCH receptions on a serving cell for which the UE is provided nrofHARQ-BundlingGroups with value - the second HARQ-ACK sub-codebook is associated with DCI format 1_3 that - schedules PDSCH receptions on more than one serving cells from the set of serving cells, or - schedules more than one PDSCH receptions on a serving cell , from the set of serving cells, for which the UE is not provided nrofHARQ-BundlingGroups or is provided nrofHARQ-BundlingGroups with value , or - does not include a SCell dormancy indication field or the SCell dormancy indication field is reserved, indicates SCell dormancy, and schedules PDSCH receptions on one or more serving cells from the set of serving cells - in the above, and for the purpose of providing HARQ-ACK information corresponding to SCell dormancy indication by the DCI format 1_3 - the UE assumes that the UE receives one PDSCH, with first SLIV in the row of pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 for DCI format 1_3, on the serving cell associated with fields in DCI format 1_3 for SCell dormancy indication, as described in Clause 10.3, and that the PDSCH provides one transport block that the UE correctly decodes, if the UE is not provided nrofHARQ-BundlingGroups for the serving cell - the UE assumes that the UE receives one or more PDSCHs associated with a TBG with smallest index, or a PDSCH reception group with smallest index, among one or more PDSCH receptions scheduled by the DCI format 1_3, on the serving cell associated with fields in DCI format 1_3 for SCell dormancy indication, as described in Clause 10.3, and that each of the one or more PDSCHs provides one transport block that the UE correctly decodes if the UE is provided nrofHARQ-BundlingGroups for the serving cell - the UE assumes incorrect decoding for transport blocks in each of the remaining PDSCH receptions scheduled by the DCI format 1_3 on the serving cell associated with fields in DCI format 1_3 for SCell dormancy indication - instead of generating HARQ-ACK information bits when harq-ACK-SpatialBundlingPUCCH is not provided, or generating HARQ-ACK information bits when harq-ACK-SpatialBundlingPUCCH is provided, for the PDSCH receptions scheduled by a DCI format 1_3, the UE generates - HARQ-ACK information bits for the PDSCH receptions scheduled by the DCI format 1_3, where is the maximum number, over the number sets of serving cells provided by MC-DCI-SetofCells in the PUCCH group, of the sum of - if nrofHARQ-BundlingGroups is not provided for a serving cell , or - if nrofHARQ-BundlingGroups is provided for the serving cell , across serving cells of a respective set of serving cells MC-DCI-SetofCells that can be scheduled PDSCH reception by a DCI format 1_3, where - is the value of maxNrofCodeWordsScheduledByDCI for serving cell if harq-ACK-SpatialBundlingPUCCH is not provided; else, ; - is the maximum number of SLIVs over all rows of the TDRA table provided by pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 for serving cell ; and - is provided by nrofHARQ-BundlingGroups for serving cell . - If for a set of serving cells provided by MC-DCI-SetofCells, is equal to the sum of - if nrofHARQ-BundlingGroups is not provided for a serving cell , or - if nrofHARQ-BundlingGroups is provided for the serving cell , across the serving cells of the set that are scheduled PDSCH receptions by a DCI format 1_3, and , the UE generates NACK values for the last HARQ-ACK information bits corresponding to the DCI format 1_3. - The counter DAI value and the total DAI value apply separately for each HARQ-ACK sub-codebook. - The UE generates the HARQ-ACK codebook by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook. If and , for obtaining a PUCCH transmission power as described in clause 7.2.1, the UE determines , where is the value of for the first Type-2 HARQ-ACK sub-codebook and is the value of for the second Type-2 HARQ-ACK sub-codebook that is determined as where - in the following - a DCI format 1_3 schedules more than one PDSCH receptions, providing transport blocks with enabled HARQ-ACK information, on more than one serving cells, or - a DCI format 1_3 schedules more than one PDSCH receptions, providing transport blocks with enabled HARQ-ACK information, on a single serving cell , for which the UE is not provided nrofHARQ-BundlingGroups or is provided nrofHARQ-BundlingGroups with value - a dormancy indication is considered as a PDSCH reception, providing a single transport block with enabled HARQ-ACK information, corresponding to the first SLIV in the row of pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3, if the UE is not provided nrofHARQ-BundlingGroups for a corresponding serving cell - a dormancy indication is considered as one or more PDSCH receptions providing respective one or more transport blocks with enabled HARQ-ACK information, corresponding to a TBG with smallest index or a PDSCH reception group with smallest index, if the UE is provided nrofHARQ-BundlingGroups for a corresponding serving cell - is the value of the total DAI field in a last DCI format 1_3 the UE detects in a last PDCCH monitoring occasion within the PDCCH monitoring occasions where the UE detects at least one DCI format 1_3. if the UE does not detect any DCI format 1_3 in any of the PDCCH monitoring occasions. - is the total number of DCI format 1_3 that the UE detects within the PDCCH monitoring occasions for the set of serving cells. if the UE does not detect any DCI format 1_3 associated with scheduling on set of serving cells in any of the PDCCH monitoring occasions. - is - if pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 is provided for at least one serving cell in the PUCCH group; - if pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 is not provided for any serving cell in the PUCCH group and harq-ACK-SpatialBundlingPUCCH is not provided; - otherwise, . - is - the number of transport blocks, in PDSCH receptions not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is not provided and nrofHARQ-BundlingGroups is not provided - the number of more than one PDSCHs, not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, scheduled by a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is provided and nrofHARQ-BundlingGroups is not provided - the number of transport block groups (TBGs) with at least one PDSCH not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, from/based on PDSCH receptions associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is not provided and nrofHARQ-BundlingGroups is provided - the number of PDSCH groups, with at least one PDSCH not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, from/based on PDSCH receptions associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is provided and nrofHARQ-BundlingGroups is provided. Table 9.1.3-1: Value of counter DAI for and of total DAI *** Unchanged parts are omitted *** TP #2B for Proposal 5 (against TS 38.213 v18.6.0) // PUCCH power control with multi-cell multi-PDSCH scheduling – Alt-2: directly modify the Rel-18 text to make it also applicable to Rel-19 MCE *** Unchanged parts are omitted *** If and , for obtaining a PUCCH transmission power as described in clause 7.2.1, the UE determines , where is the value of for the first Type-2 HARQ-ACK sub-codebook and is the value of for the second Type-2 HARQ-ACK sub-codebook that is determined as where - in the following - a DCI format 1_3 schedules more than one PDSCH receptions, providing transport blocks with enabled HARQ-ACK information, on more than one serving cells, or - a DCI format 1_3 schedules more than one PDSCH receptions, providing transport blocks with enabled HARQ-ACK information, on a single serving cell , for which the UE is not provided nrofHARQ-BundlingGroups or is provided nrofHARQ-BundlingGroups with value - a dormancy indication is considered as a PDSCH reception, providing a single transport block with enabled HARQ-ACK information, corresponding to the first SLIV in the row of pdsch-TimeDomainAllocationList or pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3, if the UE is not provided nrofHARQ-BundlingGroups for a corresponding serving cell - a dormancy indication is considered as one or more PDSCH receptions providing respective one or more transport blocks with enabled HARQ-ACK information, corresponding to a TBG with smallest index or a PDSCH reception group with smallest index, if the UE is provided nrofHARQ-BundlingGroups for a corresponding serving cell - is the value of the total DAI field in a last DCI format 1_3 the UE detects in a last PDCCH monitoring occasion within the PDCCH monitoring occasions where the UE detects at least one DCI format 1_3. if the UE does not detect any DCI format 1_3 in any of the PDCCH monitoring occasions. - is the total number of DCI format 1_3 that the UE detects within the PDCCH monitoring occasions for the set of serving cells. if the UE does not detect any DCI format 1_3 associated with scheduling on set of serving cells in any of the PDCCH monitoring occasions. - is - if pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 is provided for at least one serving cell in the PUCCH group; - if pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 is not provided for any serving cell in the PUCCH group and harq-ACK-SpatialBundlingPUCCH is not provided; - otherwise, . - is - the number of transport blocks, in PDSCH receptions not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is not provided and nrofHARQ-BundlingGroups is not provided - the number of more than one PDSCHs, not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, scheduled by a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is provided and nrofHARQ-BundlingGroups is not provided - the number of transport block groups (TBGs) with at least one PDSCH not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, from/based on PDSCH receptions associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is not provided and nrofHARQ-BundlingGroups is provided - the number of PDSCH groups, with at least one PDSCH not overlapping with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated if provided, from/based on PDSCH receptions associated with a DCI format 1_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if harq-ACK-SpatialBundlingPUCCH is provided and nrofHARQ-BundlingGroups is provided. Table 9.1.3-1: Value of counter DAI for and of total DAI *** Unchanged parts are omitted *** References: RP-242408, New WID: Multi-carrier enhancements for NR Phase 2, RAN#105, Lenovo. R1-2503155, Consolidated Rel-19 higher layers parameters list Post RAN1#120bis, Moderator (Ericsson). R1-2503547, Discussion for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling, RAN1#121, Samsung. R1-2503980, Draft CR for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling, RAN1#121, Samsung. R1-2503173, Introduction of multi-carrier enhancements for NR Phase 3 [in TS 38.213], Samsung. R1-2503174, Summary of email discussions [120bis-R19-38.213-NR_MC_enh2], Moderator (Samsung). |
| R1-2503607 Multi-cell PxSCH scheduling with a single DCI.docx |
3GPP TSG-RAN WG1 Meeting #121 R1-2503607 St Julian’s, Malta, May 19th – May 23rd, 2025 Agenda Item: 9.12.1 Source: Ericsson Title: Multi-cell PxSCH scheduling with a single DCI Document for: Discussion, Decision 1 |
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 . |
| R1-2503656.docx |
3GPP TSG RAN WG1 #121 R1-2503656 St Julian’s, Malta, May 19th – 23th, 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: Adopt the following TP for TS38.300 to remove the restrictions of same numerology among co-scheduled cells. Proposal 2: Send LS to RAN2 to convey the above TP. Proposal 3: Adopt TP1. TP1: |
| R1-2503779 Discussion on multi-cell scheduling_vfinal.docx |
3GPP TSG RAN WG1 #121 R1-2503779 St Julian’s, Malta, May 19th – 23rd, 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: Consider adopting the following TP to capture the scheduling restrictions for Rel-19 multi-cell multi-PDSCH/PUSCH scheduling in TS 38.300. Proposal 2: 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, FR2-1 and FR2-2. Multi-cell multi-PDSCH scheduling by DCI format 1_3 is applicable to FR2-1 and FR2-2. |
| R1-2503990.docx |
3GPP TSG RAN WG1 #121 R1-2503990 St Julian’s, Malta, May 19th – 23rd, 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: For TDRA-FieldIndexListDCI-1-3-r19 and TDRA-FieldIndexListDCI-0-3-r19, the maximum number of entries is 64. Proposal 2: Whether repetition and/or TBoMS is supported for Rel.19 DCI format 0-3/1-3 should be clarified. Proposal 3: RAN1 should clarify that Rel.19 DCI format 0-3/1-3 supports repetition / TBoMS with the following behavior without any specification change. For cell(s) within the set of cells configured with multi-PxSCH scheduling table, multi-PxSCH scheduling is applied, in which there is not any repetition / TBoMS is possible. For cell(s) within the set of cells only configured with regular TDRA (single-PxSCH) table, if repetition and/or TBoMS is configured in the table, repetition / TBoMS is possible. |
| R1-2504056 Remaining issues on multi-carrier enhancements for NR phase 3....docx |
3GPP TSG RAN WG1 #121 R1-2504056 St Julian’s, Malta, May 19th – 23th, 2025 Agenda item: 9.12.1 Source: China Telecom Title: Remaining issues 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: Adopt the following TP on 38.300 to support different SCS/carrier type among co-scheduled cells by a single DCI in Rel-19 and send an LS to RAN2 to convey the TP: < Unchanged parts are omitted > 10.11 Multi-cell scheduling by a single DCI Multi-cell scheduling by a single DCI allows the PDCCH of a serving cell to schedule PDSCH(s)/PUSCH(s) on one or more serving cells with the single DCI but with the following restrictions: - When a serving cell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on a cell set, the PUSCH/PDSCH on serving cells in the cell set is always scheduled by a PDCCH on the serving cell; - When SpCell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on serving cells in a cell set, that SpCell's PDSCH and PUSCH cannot be scheduled by a PDCCH on an SCell; - When an SCell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on serving cells in a cell set, SpCell is not included in the cell set; - The scheduling PDCCH and the scheduled PDSCH(s)/PUSCH(s) can use the same or different numerologies; - The co-scheduled PDSCH(s)/PUSCH(s) with a PDCCH use the same numerology, or are on FR1 licensed FDD cell(s) with one numerology and FR1 licensed TDD cell(s) with the same or the other numerology, or are on FR1 licensed FDD cell(s) with one numerology and FR2-1 cell(s) with the same or the other numerology, or are on FR1 licensed TDD cell(s) with one numerology and FR2-1 cell(s) with the same or the other numerology, or are on FR1 licensed FDD cell(s) with two different numerologies, or are on FR1 licensed TDD cell(s) with two different numerologies, or are on FR2-1 cell(s) with two different numerologies. - The co-scheduled PUSCH(s) with a PDCCH use the same numerology. < Unchanged parts are omitted > Proposal 2: Both the maximum sizes for numbers of entries of the joint TDRA tables TDRA-FieldIndexListDCI-1-3-r19 and TDRA-FieldIndexListDCI-0-3-r19 are set to 64. |
| R1-2504216 Enhancements to Multi-cell scheduling with a single DCI.docx |
3GPP TSG RAN WG1 #121 R1-2504216 St Julian’s, Malta, May 19th – 23rd, 2025 Source: OPPO Title: Enhancements to Multi-cell scheduling with a single DCI Agenda Item: 9.12.1 Document for: Discussion and Decision |
Conclusion This contribution concludes with following proposal and obsercation: Proposal 1: TS 38.300 shall be updated to support different SCSs across the cells in the set of cells. Proposal 2: The RRC parameter, nrofHARQ-BundlingGroups, for HARQ bundling for type 2 HARQ-ACK codebook is reused for Rel-19 multi-cell scheduling with a single DCI, with no additional specification impact. |
| R1-2504254_R19 MCE multi-cell scheduling_Final.DOCX |
3GPP TSG RAN WG1 #121 R1-2504254 St Julian’s, Malta, May 19th – 23th, 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 a remaining issue on the single DCI based multi-cell PDSCH/PUSCH scheduling for Rel-19, and the following proposal is provided: Proposal #1: Agree the following aspects on the construction of Type-2 HARQ-ACK codebook for Rel-19 multi-cell PDSCH scheduling: The number of HARQ-ACK information bits for each serving cell c configured with multi-PDSCH scheduling (within a set s of co-scheduled cells) is determined based on the maximum number of PDSCHs schedulable by one DCI. HARQ-ACK bits (if nrofHARQ-BundlingGroups is not provided for the serving cell c) or HARQ-ACK bits (if nrofHARQ-BundlingGroups is provided for the serving cell c) NACK value is padded for the last HARQ-ACK information bits if , where is the sum of or across the cells within the set s of co-scheduled cells. |
| R1-2504274.docx |
3GPP TSG RAN WG1 #121 R1-2504274 St Julians, Malta, 19th – 23rd May, 2025 Agenda item: 9.12.1 Source: MediaTek Inc. Title: Multi-carrier enhancements for NR Phase 2 Document for: Discussion and Decision |
Conclusion The following proposals are made. Proposal 1: Agree the following: When the UE is scheduled with multiple PDSCHs on a serving cell by a DCI 0-3/1-3, the bits of rv field and NDI field, respectively, in the DCI are one-to-one mapped to the scheduled PDSCH(s) indicated by the TDRA information field with the corresponding transport block(s) in the scheduled order starting from LSB, where the LSB bits of the rv field and NDI field, respectively, correspond to the first scheduled PDSCH indicated by the TDRA information field. [Where there is more than one bit in the rv field for each scheduled PxSCH, the first information bit shall correspond to the higher order bit and the last bit the lower order bit.] Proposal 2: Maximum number of entries in the joint TDRA table for 0_3/1_3 in Rel-19 when multiple PxSCHs are configured is limited to 64. |
| R1-2504415 Multi-cell scheduling with a single DCI.docx |
3GPP TSG RAN WG1 Meeting #121 R1-2504415 St Julian’s, Malta, May 19th – 23st, 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: The value range of TDRA-FieldIndexListDCI-1-3-r19 is updated to SEQUENCE (SIZE (1..64FFS)) OF TDRA-FieldIndexDCI-1-3-r19 The value range of TDRA-FieldIndexListDCI-0-3-r19 is updated to SEQUENCE (SIZE (1..64FFS)) OF TDRA-FieldIndexDCI-0-3-r19 |
| R1-2504519_DCM_Discussion on R19 MCE.docx |
3GPP TSG RAN WG1 #121 R1-2504519 St Julian’s, Malta, May 19th – 23rd, 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 an observation and proposals. Observation 1: 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. Proposal 1: TP below for TS38.300 should be endorsed for the removal of the restriction for the numerology between co-scheduled PDSCH(s)/PUSCH(s) to support different SCS/carrier type among co-scheduled cells. Proposal 2: Unless there is any technical issue, time domain HARQ-ACK bundling is supported for both types-1 and type-2 HARQ codebook in Rel-19 multi-cell multi-PDSCH scheduling. Proposal 3: For TDRA-FieldIndexListDCI-1(0)-3-r19, the maximum number of entries with up to 64 has sufficient flexibility and larger maximum size than 64 would not be necessary. Proposal 4: The existing RRC parameters of both nrofHARQ-BundlingGroups-r17 for type-2 HARQ CB and timeDomainHARQ-BundlingType1-r17 for type-1 HARQ CB can be reused for time domain HARQ bundling in Rel-19 multi-cell multi-PDSCH scheduling. |
| R1-2504761.docx |
3GPP TSG RAN WG1 Meeting #121 R1-2504761 St Julian’s, Malta, May 19th – 23rd, 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 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 . |
| R1-2504762.docx |
3GPP TSG RAN WG1 Meeting #121 R1-2504762 St Julian’s, Malta, May 19th – 23rd, 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 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 . Agreements made in RAN1#121 Agreement Below TP for TS38.300 is adopted for Rel-19 MCE. Send an LS to RAN2 to convey the above TP. Agreement For a cell within a cell set configured to be schedulable by a DCI format 0_3, the network does not configure pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3 simultaneously with the numberOfSlotsTBoMS-r17 and/or pusch-AggregationFactor. Add above to RRC parameter list. Agreement Agreement For Type-2 HARQ-ACK codebook, adopt TP1 in Section 8 of R1-2504761 to Section 9.1.3.1, TS38.213. Agreement For PUCCH power control, adopt TP2A in Section 8 of R1-2504761 to Section 9.1.3.1, TS38.213. Agreement Support maximum 64 rows for TDRA-FieldIndexListDCI-1-3-r19. Support maximum 128 rows for TDRA-FieldIndexListDCI-0-3-r19. Agreement Draft LS R1-2504764 is endorsed in principle. Agreement Final LS R1-2504861 is endorsed. |
| R1-2504763.zip |
TDoc file unavailable |