Conclusion
This contribution concludes with following proposals:
Proposal 1: Design a Rel-19 UE feature group for multi-cell scheduling with a single DCI, as following:
FG X-1: Multi-cell PUSCH/PDSCH scheduling by DCI format 0_3/1_3 with different SCS among cells in a co-scheduled cell set, with up to one PUSCH/PDSCH per cell.
Component 1: UE supports monitoring DCI format 0_3/1_3 for UL/DL scheduling with up to two different SCS between cells in the set;
Component 2: The co-scheduled cells have different SCS and/or different carrier type. The candidate values on the differentiations among the co-scheduled cells include: {different SCS and different carrier type, different SCS and same carrier type, same SCS and different carrier type}.
Prerequisite: At least one of {FG49-1, FG49-2}
FG X-2: Multi-cell PUSCH/PDSCH scheduling by DCI format 0_3/1_3 with multiple PUSCHs/PDSCHs on a co-scheduled cell and the same SCS among cells in a co-scheduled cell set:
Component 1: UE supports monitoring DCI format 0_3/1_3 for multi-PDSCH/PUSCH scheduling on one cell with the same SCS and the same carrier type among cells in a co-scheduled cell set.
Component 2: Supported maximum number of PUSCHs/PDSCHs on a co-scheduled cell by a DCI format 0_3/1_3, candidate values: {2,3,4,5,6,7,8}.
Component 3: Supported HARQ feedback types, candidate values: {type 1, type2, type 1 and type 2}, Note: the UE shall report the same value for all supported BC for FG X-2.
Prerequisite: At least one of {FG49-1, FG49-2}
FG X-3: Multi-cell PUSCH/PDSCH scheduling by DCI format 0_3/1_3 with multiple PUSCHs/PDSCHs on a co-scheduled cell and different SCS among cells in a co-scheduled cell set:
Component 1: UE supports monitoring DCI format 0_3/1_3 for multi-PDSCH/PUSCH scheduling on one cell with up to two different SCS among cells in the set.
Component 2: Supported maximum number of PUSCHs/PDSCHs on a scheduled cell by a DCI format 0_3/1_3, candidate values: {2,3,4,5,6,7,8}.
Component 3: Supported HARQ feedback types, candidate values: {type 1, type2, type 1 and type 2}, Note: the UE shall report the same value for all supported BC for FG X-3.
Prerequisite: At least one of {FG49-1, FG49-2}, FG X-1.
A preliminary UE feature table based on above discussions is given in the Appendix.
|
Conclusions
This contribution considered UE features for Rel-19 multi-cell scheduling enhancements and made the following proposals.
Proposal 1: For MC-DCI with different SCS or different carrier types:
RAN1 to specify UE features corresponding to Cases 1, 2, and 3, as captured in the RAN1#118bis agreement;
Deprioritize Cases 4, 5, and 6 (mixed SCS for a same carrier type).
Proposal 2: Adopt the following for the new FG 49-X for DL MC-DCI 1_3 with different SCS and/or carrier types:
Title of: Multi-cell PDSCH scheduling by DCI format 1_3 on a set of cells with different carrier types (and with same or different SCS);
Components 2, 4 – 9, and 11 directly follow from FG 49-1 without any change;
Components 1/3/10 are updated based on FG 49-1 as follows:
UE supports monitoring DCI format 1_3 for DL scheduling with different SCS and/or different carrier type between scheduling cell and cells in the set.
The scheduling is included or not included in the set of cells, and is in a same PUCCH group as the set of cells.
3) Scheduling cell and co-scheduled cells have same or different SCS, and same or different carrier type.
The set of co-scheduled cells have one or two different SCS values, and two different carrier types, by indicating support / not-support for one or multiple of the following cases.
Note: detailed signaling design is up to RAN2.
Case 1-1: Scheduled cells include {FR1 licensed FDD cell(s) with SCS1 and FR1 licensed TDD cell(s) with SCS2} and {SCS1 same as SCS2}
Scheduling cell from candidate value {FR1 licensed FDD, FR1 licensed TDD}
Case 1-1a: Scheduling cell with SCS3 same as SCS1/SCS2
Case 1-1b: Scheduling cell with SCS3 from candidate value: {SCS3 lower than SCS1/SCS2, SCS3 higher than SCS1/SCS2, both}
FFS whether to merge Case 1-1a and Case 1-1b
Case 1-2: Scheduled cells include {FR1 licensed FDD cell(s) with SCS1 and FR1 licensed TDD cell(s) with SCS2} and {SCS1 different from SCS2}
Scheduling cell from candidate value {FR1 licensed FDD, FR1 licensed TDD}
Case 1-2a: Scheduling cell with SCS3 from candidate value: {SCS3 equal to min {SCS1, SCS2}, SCS3 equal to max {SCS1, SCS2}, both}
Case 1-2b: Scheduling cell with SCS3 from candidate value: {SCS3 lower than min {SCS1, SCS2}, SCS3 higher than max {SCS1, SCS2}, both}
FFS whether to merge Case 1-2a and Case 1-2b
FFS Case 1-2c: Scheduling cell with SCS3 strictly between SCS1 and SCS2
FFS Case 2-1: Scheduled cells include {FR1 licensed FDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2} and {SCS1 same as SCS2}
Scheduling cell from candidate value {FR1 licensed FDD, FR1 licensed TDD}
Case 2-1a: Scheduling cell with SCS3 same as SCS1/SCS2
Case 2-1b: Scheduling cell with SCS3 lower than SCS1/SCS2
Note 1: Only SCS1 = SCS2 = 60 kHz is applicable for Case 2-1
Note 1: SCS3 higher than SCS1/SCS2 does not apply when the scheduling cell is in FR1
FFS whether to merge Case 2-1a and Case 2-1b
Case 2-2: Scheduled cells include {FR1 licensed FDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2} and {SCS1 different from SCS2}
Scheduling cell from candidate value {FR1 licensed FDD, FR1 licensed TDD}
Case 2-2a: Scheduling cell with SCS3 from candidate value: {SCS3 equal to min {SCS1, SCS2}, [FFS SCS3 equal to max {SCS1, SCS2}, FFS both]}
Case 2-2b: Scheduling cell with SCS3 lower than min {SCS1, SCS2}
Note: SCS3 higher than max {SCS1, SCS2} does not apply when the scheduling cell is in FR1
FFS whether to merge Case 2-2a and Case 2-2b
FFS Case 2-2c: Scheduling cell with SCS3 strictly between SCS1 and SCS2
FFS Case 3-1: Scheduled cells include {FR1 licensed TDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2} and {SCS1 same as SCS2}
Scheduling cell from candidate value {FR1 licensed FDD, FR1 licensed TDD}
Case 3-1a: Scheduling cell with SCS3 same as SCS1/SCS2
Case 3-1b: Scheduling cell with SCS3 lower than SCS1/SCS2
Note 1: Only SCS1 = SCS2 = 60 kHz is applicable for Case 3-1
Note 1: SCS3 higher than SCS1/SCS2 does not apply when the scheduling cell is in FR1
FFS whether to merge Case 3-1a and Case 3-1b
Case 3-2: Scheduled cells include {FR1 licensed TDD cell(s) with SCS1 and FR2-1 cell(s) with SCS2} and {SCS1 different from SCS2}
Scheduling cell from candidate value {FR1 licensed FDD, FR1 licensed TDD}
Case 3-2a: Scheduling cell with SCS3 from candidate value: {SCS3 equal to min {SCS1, SCS2}, [FFS SCS3 equal to max {SCS1, SCS2}, FFS both]}
Case 3-2b: Scheduling cell with SCS3 lower than min {SCS1, SCS2}
Note: SCS3 higher than max {SCS1, SCS2} does not apply when the scheduling cell is in FR1
FFS whether to merge Case 3-2a and Case 3-2b
FFS Case 3-2c: Scheduling cell with SCS3 strictly between SCS1 and SCS2
10a) The number of unicast DL DCIs to process per slot of scheduling cell for a set of cells configured for multi-cell PDSCH scheduling by DCI format 1_3:
One DCI format 1_3 for the set of cells and,
One unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells that are not scheduled by DCI 1_3
Applies for same SCS.
Applies for low-to-high SCS (i.e., scheduling cell has lower SCS than at least some cells from the set of cells, and same SCS as remaining cells in the set of cells, if any).
10b) The number of unicast DL DCIs to process per max {N1, N2} consecutive slots of scheduling cell for a set of cells configured for multi-cell PDSCH scheduling by DCI format 1_3:
One DCI format 1_3 for the set of cells and,
unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS1 that are scheduled by DCI 1_3
unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS2 that are scheduled by DCI 1_3
unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS1 that are not scheduled by DCI 1_3
unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS2 that are not scheduled by DCI 1_3
Applies for high-to-low SCS (i.e., scheduling cell has higher SCS than at least some cells from the set of cells, and same SCS as remaining cells in the set of cells, if any), N1 and N2 are based on pair of (scheduling CC SCS, respective scheduled CC SCS), i.e., N1 = ratio of (SCS3, SCS1) and N2 = ratio of (SCS3, SCS2) per description in component 3: N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N = 8 for (120,15)
FFS the number of unicast DL DCIs when scheduling CC SCS is strictly in between scheduled CC SCS, if supported
Proposal 3: For R19 UE features for multi-PDSCH/PUSCH scheduling with DCI format 0_3/1_3:
Consider the supported scenarios in Rel-17 52.6GHz WI (e.g., FR2-2 or 120 kHz for FR2-1) as baseline.
References:
RP-242408, New WID: Multi-carrier enhancements for NR Phase 2, RAN#105, Lenovo.
TS 38.822, v18.0.0.
R1-2501377, Feature lead summary #4 on multi-cell scheduling with a single DCI, RAN1#120, Moderator (Lenovo).
R1-2409166, Feature lead summary #5 on multi-cell scheduling with a single DCI, RAN1#118bis, Moderator (Lenovo). |
Conclusion
In this contribution, we made the following proposals on UE FG for multi-carrier enhancements in Rel-19:
Proposal 1:
UE FG XX: If UE reports this FG, then UE supports multi-cell multi-PDSCH scheduling by DCI format 1_3 on a scheduling cell (within the set) with same/different SCS and/or same/different carrier type between the cells in the set is proposed with following details:
Component 1: UE supports monitoring DCI format 1_3 for DL scheduling with same/different SCS and/or same different carrier type between the cells in the set
Component 2: Scheduling cell is PCell if set of cells includes PCell, and scheduling cell is PCell or an SCell if set of cells includes only SCells
Component 3a: Combination of carrier type and SCS value cells within the set can be reported from the following value set including {same SCS-same carrier type, same SCS-different carrier type, different SCS-same carrier type, different SCS-different carrier type}
Component 3b: If different SCS among the cells within the set is reported by component 3a, then UE can report that scheduling cell and co-scheduled cells have different SCS with candidate values including {Scheduling cell of lower SCS and scheduled cells of higher SCS, Scheduling cell of higher SCS and scheduled cells of lower SCS, both}
Component 4: Following candidate values for combination of SCS and carrier type can be reported depending on the reported Component 3a:
For same SCS-same carrier type, value set includes {FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1, FR2-2} and UE reports one or multiple of values from the value set
For same SCS-different carrier type, value set includes {FR1 licensed FDD-FR1 licensed TDD, FR1 licensed-FR2-1, FR1 licensed TDD-FR2-1} and UE reports one or multiple of values from the value set
For different SCS-same carrier type, value set includes {FR1 licensed FDD:15kHz-30kHz, FR1 licensed TDD:15kHz-30kHz, FR2-1:60kHz-120kHz} and UE reports one or multiple of values from the value set
For different SCS-different carrier type, value set includes {FR1 licensed FDD:15kHz-FR1 licensed TDD:30kHz, FR1 licensed FDD:30kHz-FR1 licensed TDD:15kHz, FR1 licensed FDD:15kHz-FR2-1:60kHz, FR1 licensed FDD:15kHz-FR2-1:120kHz, FR1 licensed FDD:30kHz-FR2-1:60kHz, FR1 licensed FDD:30kHz-FR2-1:120kHz, FR1 licensed TDD:15kHz-FR2-1:60kHz, FR1 licensed TDD:15kHz-FR2-1:120kHz, FR1 licensed TDD:30kHz-FR2-1:60kHz, FR1 licensed TDD:30kHz-FR2-1:120kHz}
Component 5: Max number of co-scheduled cells per set of cells supported by UE is reported with candidate value set of {2, 3, 4}
Component 6: Max number of PDSCHs per co-scheduled cells per set of cells and max number of PDSCHs across all the co-scheduled cells pet set of cells supported by UE is reported with candidate value set combination of {2:4,2:6,2:8,4:4,4:8,4:12,4:16,8:8, 8:16}
Component 7: Max number of sets of cells supported by UE across PUCCH groups: Candidate value set of {1, 2, 3, 4, 5, 6, 7, 8}
Component 8: Max number of sets of cells supported by UE for a same scheduling cell: Candidate value set of {1, 2, 3, 4}
Component 9: Supported HARQ feedback types, candidate values: {type 1, type2, type 1 and type 2}, Note: the UE shall report the same value for all supported BC for FG 49-1
Component 10: Supported co-scheduled cell indication schemes: Candidate value set of {FDRA field based, co-scheduled cell indicator field based, both}
Component 11: Support Type-2 for ‘Antenna port(s)’ field
Component 12: The number of unicast DL DCIs to process per N consecutive slots of scheduling cell for a set of cells configured for multi-cell multi-PDSCH scheduling by DCI format 1_3
One DCI format 1_3 for the set of cells and,
One unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells that are not scheduled by DCI 1_3
For same SCS across scheduling cell and all the co-scheduled cells within the set, N = 1
For low-to-highest SCS, N = 1, where highest SCS corresponds the the maximum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cell within the set is higher than the SCS of the scheduling cell
For high-to-lowest SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N=8 for (120,15), where lowest SCS corresponds the the minimum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cells within the set is lower than the SCS of the scheduling cell
Component 13: Monitoring SS set(s) for DCI format 1_3 for a set of cells for the following cases:
Search space set configuration for DCI format 1_3 for the set of cells is provided only on the scheduling cell, or;
If the scheduling cell is outside the set of cells, then Search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being NOT in the set of cells and that serving cell in the set of cells should be associated with
the SCS that is at least not higher than the SCS of the scheduling cell
If the scheduling cell is also within the set of cells, then UE can additionally report with this capability that the Search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells
Proposal 2:
UE FG YY: If UE reports this FG, then UE supports multi-cell multi-PUSCH scheduling by DCI format 0_3 on a scheduling cell (within the set) with same/different SCS and/or same/different carrier type between the cells in the set is proposed with following details:
Component 1: UE supports monitoring DCI format 0_3 for UL scheduling with same/different SCS and/or same different carrier type between the cells in the set
Component 2: Scheduling cell is PCell if set of cells includes PCell, and scheduling cell is PCell or an SCell if set of cells includes only SCells
Component 3a: Combination of carrier type and SCS value cells within the set can be reported from the following value set including {same SCS-same carrier type, same SCS-different carrier type, different SCS-same carrier type, different SCS-different carrier type}
Component 3b: If different SCS among the cells within the set is reported by component 3a, then UE can report that scheduling cell and co-scheduled cells have different SCS with candidate values including {Scheduling cell of lower SCS and scheduled cells of higher SCS, Scheduling cell of higher SCS and scheduled cells of lower SCS, both}
Component 4: Following candidate values for combination of SCS and carrier type can be reported depending on the reported Component 3a:
For same SCS-same carrier type, value set includes {FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1, FR2-2} and UE reports one or multiple of values from the value set
For same SCS-different carrier type, value set includes {FR1 licensed FDD-FR1 licensed TDD, FR1 licensed-FR2-1, FR1 licensed TDD-FR2-1} and UE reports one or multiple of values from the value set
For different SCS-same carrier type, value set includes {FR1 licensed FDD:15kHz-30kHz, FR1 licensed TDD:15kHz-30kHz, FR2-1:60kHz-120kHz} and UE reports one or multiple of values from the value set
For different SCS-different carrier type, value set includes {FR1 licensed FDD:15kHz-FR1 licensed TDD:30kHz, FR1 licensed FDD:30kHz-FR1 licensed TDD:15kHz, FR1 licensed FDD:15kHz-FR2-1:60kHz, FR1 licensed FDD:15kHz-FR2-1:120kHz, FR1 licensed FDD:30kHz-FR2-1:60kHz, FR1 licensed FDD:30kHz-FR2-1:120kHz, FR1 licensed TDD:15kHz-FR2-1:60kHz, FR1 licensed TDD:15kHz-FR2-1:120kHz, FR1 licensed TDD:30kHz-FR2-1:60kHz, FR1 licensed TDD:30kHz-FR2-1:120kHz}
Component 5: Max number of co-scheduled cells per set of cells supported by UE is reported with candidate value set of {2, 3, 4}
Component 6: Max number of PDSCHs per co-scheduled cells per set of cells and max number of PDSCHs across all the co-scheduled cells pet set of cells supported by UE is reported with candidate value set combination of {2:4,2:6,2:8,4:4,4:8,4:12,4:16,8:8, 8:16}
Component 7: Max number of sets of cells supported by UE across PUCCH groups: Candidate value set of {1, 2, 3, 4, 5, 6, 7, 8}
Component 8: Max number of sets of cells supported by UE for a same scheduling cell: Candidate value set of {1, 2, 3, 4}
Component 9: Supported co-scheduled cell indication schemes: Candidate value set of {FDRA field based, co-scheduled cell indicator field based, both}
Component 10: Support Type-2 for ‘Antenna port(s)’, ‘Precoding information and number of layers’ and ‘SRS resource indicator’ fields
Component 11: The number of unicast UL DCIs to process per N consecutive slots of scheduling cell for a set of cells configured for multi-cell multi-PUSCH scheduling by DCI format 0_3
For FDD scheduling cell
Up to 1 DCI format 0_3 for the set of cells and,
Up to 1 unicast DL DCI formats 0_0/0_1/0_2 (if supported) for each of the cells that are not scheduled by DCI 0_3
For a cell in a set of cells, no more than 2 DCI scheduling multi-PUSCH for the cell
For TDD scheduling cell
Up to 2 DCI format 0_3 for the set of cells and,
Up to 2 unicast DL DCI formats 0_0/0_1/0_2 (if supported) for each of the cells that are not scheduled by DCI 0_3
For a cell in a set of cells, no more than 2 DCI scheduling multi-PUSCH for the cell
For same SCS across scheduling cell and all the co-scheduled cells within the set, N = 1
For low-to-highest SCS, N = 1, where highest SCS corresponds the the maximum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cell within the set is higher than the SCS of the scheduling cell
For high-to-lowest SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N = 8 for (120,15), where lowest SCS corresponds the the minimum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cells within the set is lower than the SCS of the scheduling cell
Component 12: Monitoring SS set(s) for DCI format 0_3 for a set of cells for the following cases
Search space set configuration for DCI format 0_3 for the set of cells is provided only on the scheduling cell, or;
If the scheduling cell is outside the set of cells, then Search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being NOT in the set of cells and that serving cell in the set of cells should be associated with
Option 3: the SCS that is at least not higher than the SCS of the scheduling cell
If the scheduling cell is also within the set of cells, then UE can additionally report with this capability that the Search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells
|