Content for TR 38.835 Word version: 18.0.1

1… 4… 5… 6 A B… B.1.2 B.1.3 B.1.4 B.1.5 B.1.6 B.1.7 B.1.8 B.1.9 B.1.10 B.2… B.2.2 B.2.3 B.2.4 B.2.5 B.2.6 B.2.7 B.2.8 B.2.9 B.2.10 B.2.11 B.2.12 B.2.13 B.2.14 B.2.15 B.2.16 B.2.17 B.2.18 C…

B.1 Capacity performance evaluation results B.1.1 Multi-PDSCH scheduling by a single DCI
...

B Evaluation Studies p. 18

B.1 Capacity performance evaluation results p. 18

B.1.1 Multi-PDSCH scheduling by a single DCI p. 18

This clause captures the capacity performance evaluation results for dynamic scheduling when multi-PDSCH is scheduled by a single DCI. Due to large XR video frame as per 38.838, resources in a single slot may be not enough to convey all the data of a frame, resulting in resource allocation spanning more than one slot. Thereby, in this clause, multi-PDSCH scheduling by a single DCI is evaluated to transmit XR video frame over multiple slots.

The performance of single-PDSCH scheduling, where X symbol(s) are always reserved for PDCCH transmission in each slot (scheme 1.1 in Tables B.1.1-1,2,3) has been compared against various schemes for multi-PDSCH scheduling. Particularly, the following schemes, where multi-PDSCH is scheduled by a single DCI, have been evaluated:

Scheme 1.2: Multi-PDSCH scheduling, where unoccupied CORESET in a slot can be re-used for PDSCH transmission.
Scheme 1.3: Multi-PDSCH scheduling, where X symbol(s) are always reserved for PDCCH transmission in each slot.
Scheme 1.4: Multi-PDSCH scheduling with FDRA enhancement - more than one FDRA indication is contained in the scheduling DCI, each of which is applied to one or more scheduled PDSCH.
Scheme 1.5: Multi-PDSCH scheduling enhancement with early HARQ-ACK feedback - multiple PUCCHs may be considered where HARQ-ACK for the earlier PDSCH(s) can be reported earlier than the later PDSCH(s) scheduled by the same DCI, to reduce latency of HARQ-ACK feedback.
Scheme 1.6: Multi-PDSCH scheduling where single PDCCH schedules up to 4 PDSCHs and full flexibility in terms of resource (RB allocation) as well as MCS for each of the 4 PDSCHs.
Scheme 1.7: Multi-PDSCH scheduling, where X symbols per slot are used for PDCCH if there is at least one UE that needs to be scheduled with first TB out of multiple TBs and 0 symbols per slot are used for PDCCH if no UE with the first TB out of multiple TBs needs to be scheduled.

The performance results of the above schemes are reported in Table B.1.1-1, Table B.1.1-2, Table B.1.1-3 in terms of the ratio of satisfied users.

Table B.1.1-1: FR1, DL, InH, VR/AR and Cloud Gaming at 60 FPS

Source	Tdoc Source	Scheme	TDD format	SU/MU-MIMO	Data rate (Mbps)	PDB (ms)	Capacity (UEs/cell)	C1=floor (Capacity)	% of satisfied UEs when #UEs/cell = C1	Notes
Source [vivo]	R1-2208661	1.1*	DDDSU	SU-MIMO	30	10	9.8	9	96.61%	Note 1,3
Source [vivo]	R1-2208661	1.1*	DDDSU	SU-MIMO	45	10	6.08	6	91.67%	Note 1,3
Source [vivo]	R1-2208661	1.1**	DDDSU	SU-MIMO	30	10	8.16	8	91.07%	Note 1,3
Source [vivo]	R1-2208661	1.1**	DDDSU	SU-MIMO	45	10	4.66	4	97.22%	Note 1,3
Source [vivo]	R1-2208661	1.1***	DDDSU	SU-MIMO	30	10	10.25	10	93.06%	Note 1,3
Source [vivo]	R1-2208661	1.2*	DDDSU	SU-MIMO	30	10	10.37	10	95%	Note 1,2,3
Source [vivo]	R1-2208661	1.2*	DDDSU	SU-MIMO	45	10	6.27	6	94.91%	Note 1,2,3
Source [vivo]	R1-2208661	1.2**	DDDSU	SU-MIMO	30	10	9.58	9	95.14%	Note 1, 2,3
Source [vivo]	R1-2208661	1.2**	DDDSU	SU-MIMO	45	10	5.57	5	96.67%	Note 1, 2,3
Source [vivo]	R1-2208661	1.2***	DDDSU	SU-MIMO	30	10	10.1	10	91.28%	Note 1, 2,3
Source [vivo]	R1-2208661	1.3*	DDDSU	SU-MIMO	30	10	8.81	8	93.89%	Note 1,3
Source [vivo]	R1-2208661	1.3**	DDDSU	SU-MIMO	30	10	7.25	7	92.02%	Note 1,3
Source [vivo]	R1-2208661	1.3***	DDDSU	SU-MIMO	30	10	9.68	9	98.37%	Note 1,3
Source [vivo]	R1-2208661	1.4*	DDDSU	SU-MIMO	30	10	11.09	11	90.8%	Note 1,2
Source [vivo]	R1-2208661	1.5*	DDDSU	SU-MIMO	30	10	10.59	10	95.72%	Note 1,2
Source [InterDigital]	R1-2209658	1.1**	DDDSU	SU-MIMO	30	10	5.3	5	94%	Note 1
Source [InterDigital]	R1-2209658	1.1**	DDDSU	SU-MIMO	45	10	3.1	3	91.5%	Note 1
Source [InterDigital]	R1-2209658	1.1**	DDDSU	SU-MIMO	30	15	7.2	7	94.5%	Note 1
Source [InterDigital]	R1-2209658	1.6****	DDDSU	SU-MIMO	30	10	7.8	7	97%	Note 1,2
Source [InterDigital]	R1-2209658	1.6****	DDDSU	SU-MIMO	45	10	4.1	4	91%	Note 1,2
Source [InterDigital]	R1-2209658	1.6****	DDDSU	SU-MIMO	30	15	10	10	100%	Note 1,2
Source [ZTE]	R1-2209198	1.1**	DDDSU	SU-MIMO	30	10	9.1	9	91%	Note 1
Source [ZTE]	R1-2209198	1.1**	DDDSU	SU-MIMO	60	10	3.4	3	97%	Note 1
Source [ZTE]	R1-2209198	1.7**	DDDSU	SU-MIMO	30	10	7.9	7	96%	Note 1,2,4
Source [ZTE]	R1-2209198	1.7**	DDDSU	SU-MIMO	60	10	3.7	3	99%	Note 1,2,4
NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1,4,4) NOTE 2: No symbol for PDCCH is reserved in the slot where no scheduling DCI is transmitted NOTE 3: Results does not consider any other PDCCH that may occupy the CORESET(s) than scheduling DCI, e.g. broadcast PDCCH NOTE 4: Results consider 2 symbols are used for PDCCH, if at least one UE needs to be scheduled with the first TB out of multiple TBs * Number of PDCCH symbols per slot = 1 Number of PDCCH symbols per slot = 2 * Number of PDCCH symbols per slot = 0.5 **** Number of PDCCH symbols per slot = 4

Table B.1.1-2: FR1, DL, DU, VR/AR and Cloud Gaming at 60 FPS

Source	Tdoc Source	Scheme	TDD format	SU/MU-MIMO	Data rate (Mbps)	PDB (ms)	Capacity (UEs/cell)	C1=floor (Capacity)	% of satisfied UEs when #UEs/cell = C1	Notes
Source [InterDigital]	R1-2209658	1.1**	DDDSU	SU-MIMO	30	10	5.5	5	95%	Note 1
Source [InterDigital]	R1-2209658	1.1**	DDDSU	SU-MIMO	45	10	3.7	3	100%	Note 1
Source [InterDigital]	R1-2209658	1.1**	DDDSU	SU-MIMO	30	15	7.5	7	95%	Note 1
Source [InterDigital]	R1-2209658	1.6****	DDDSU	SU-MIMO	30	10	8.4	8	94.5%	Note 1
Source [InterDigital]	R1-2209658	1.6****	DDDSU	SU-MIMO	45	10	5.1	5	91.5%	Note 1
Source [InterDigital]	R1-2209658	1.6****	DDDSU	SU-MIMO	30	15	9.1	9	91%	Note 1
NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,2,2,1,1:8,2) * Number of PDCCH symbols per slot = 1 Number of PDCCH symbols per slot = 2 * Number of PDCCH symbols per slot = 0.5 **** Number of PDCCH symbols per slot = 4

Table B.1.1-3: FR1, DL, UMa, VR/AR at 60 FPS

Source	Tdoc Source	Scheme	TDD format	SU/MU-MIMO	Data rate (Mbps)	PDB (ms)	Capacity (UEs/cell)	C1=floor (Capacity)	% of satisfied UEs when #UEs/cell = C1	Notes
Source [ZTE]	R1-2209198	1.1**	DDDSU	SU-MIMO	30	10	8.8	8	97%	Note 1
Source [ZTE]	R1-2209198	1.7**	DDDSU	SU-MIMO	30	10	7.6	7	96%	Note 1,2,4
NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8) NOTE 2: No symbol for PDCCH is reserved in the slot where no scheduling DCI is transmitted NOTE 3: Results did not consider any other PDCCH that may occupy the CORESET(s) than scheduling DCI, e.g. broadcast PDCCH NOTE 4: Results consider 2 symbols are used for PDCCH, if the slot is not the first slot of multiple TB scheduling for one UE but is the first slot of multiple TBs scheduling or the slot of single TB scheduling for another UE * Number of PDCCH symbols per slot = 1 Number of PDCCH symbols per slot = 2 * Number of PDCCH symbols per slot = 0.5 **** Number of PDCCH symbols per slot = 4

Based on the evaluation results in Table B.1.1-1 and Table B.1.1-3, the following observations regarding multi-PDSCH scheduling by a single DCI as compared to single PDSCH scheduling can be made:

For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is decreased from 9.8 UEs per cell with single-PDSCH scheduling to 8.81 UEs per cell with multi-PDSCH scheduling, where 1 symbol is always reserved for PDCCH transmission in each slot (capacity drop is -10%). Similar trend is observed when number of PDCCH symbols per slot is equal to 0.5 or 2 symbols.
For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 9.8 UEs per cell with single-PDSCH scheduling to 10.37 UEs per cell with multi-PDSCH scheduling, where unoccupied CORESET in a slot can be re-used for PDSCH transmission (1 symbol for PDCCH transmission in each slot) (capacity gain is 6%). For VR/AR single-stream traffic model, 45Mbps, 10ms PDB, the results show similar trend.
For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is decreased from 10.25 UEs per cell with single-PDSCH scheduling to 10.1 UEs per cell with multi-PDSCH scheduling, where unoccupied CORESET in a slot can be re-used for PDSCH transmission (0.5 for PDCCH transmission in each slot) (capacity drop is -1.46%).
For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [ZTE] that the capacity is decreased from 9.1 UEs per cell with single-PDSCH scheduling to 7.9 UEs per cell with multi-PDSCH scheduling, where 2 symbols per slot are used for PDCCH if there is at least one UE that needs to be scheduled with first TB out of multiple TBs (capacity drop is -13%). For FR1, UMa scenario, the results show similar trend.
For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 60Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.4 UEs per cell with single-PDSCH scheduling to 3.7 UEs per cell with multi-PDSCH scheduling, where 2 symbols per slot are used for PDCCH if there is at least one UE that needs to be scheduled with first TB out of multiple TBs (capacity gain is 8%).

Based on the evaluation results in Table B.1.1-1 and Table B.1.1-2, the following observations regarding enhanced multi-PDSCH scheduling by a single DCI can be made:

For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 10.37 UEs per cell with multi-PDSCH scheduling to 10.59 UEs per cell with multi-PDSCH scheduling enhancement of early HARQ-ACK feedback (unoccupied CORESET in a slot can be re-used for PDSCH transmission, 1 symbol for PDCCH transmission in each slot) (capacity gain is 2.12%).
For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 10.37 UEs per cell with multi-PDSCH scheduling to 11.09 UEs per cell with multi-PDSCH scheduling FDRA enhancement (unoccupied CORESET in a slot can be re-used for PDSCH transmission, 1 symbol for PDCCH transmission in each slot) (capacity gain is 7%).
For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 5.3 UEs per cell with single-PDSCH scheduling to 7.2 UEs per cell with multi-PDSCH scheduling, where single PDCCH schedules up to 4 PDSCHs/PUSCHs and full flexibility in terms of resource (RB allocation) as well as MCS for each of the 4 PDSCHs/PUSCHs (capacity gain is 36%). For VR/AR single-stream traffic model, 45Mbps, 10ms PDB and for CG single-stream traffic model, 15ms PDB, the results show similar trend.
For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 5.5 UEs per cell with single-PDSCH scheduling to 8.4 UEs per cell with multi-PDSCH scheduling, where single PDCCH schedules up to 4 PDSCHs/PUSCHs and full flexibility in terms of resource (RB allocation) as well as MCS for each of the 4 PDSCHs/PUSCHs (capacity gain is 53%). For VR/AR single-stream traffic model, 45Mbps, 10ms PDB and for CG single-stream traffic model, 15ms PDB, the results show similar trend.