Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 38.835  Word version:  18.0.1

Top   Top   Up   Prev   Next
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.6  Configured grant schedulingp. 29

This clause captures the capacity performance evaluation results for configured grant scheduling. A UE can transmit UL data using CG resources after configuration (of a CG Config Type 1) or activation (of a CG Config Type 2), without the need of receiving UL grant from the gNB.
The performance of dynamic grant (DG) scheduling has been compared against configured grant (CG) scheduling. Particularly, the following schemes have been evaluated:
  • Scheme 6.1.1: DG scheduling with SR followed by UL grant with BSR and data. It is assumed that an SR is triggered upon arrival of a new XR packet in the UE buffer. An UL resource is then granted to the UE to transmit BSR and a number of UL data. A periodicity of SR and a size of initial UL grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.1.2: DG scheduling with SR followed by UL grant with BSR only. A periodicity of SR may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.2: Pre-scheduling dynamic grant: The scheduling is based on dynamic grants where it is assumed that the network is provided with XR traffic periodicity. An initial grant to the UE when its traffic is expected is transmitted (implementation-based learning) without using SR. A size of initial UL grant may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.3: Dynamic scheduling with genie BSR (DG with genie BSR): The scheduling is based on dynamic grants where it is assumed BSR is available with zero delay at the scheduler when a new XR packet arrives in the UE buffer, to be used for indicating UL grants to the UE. Hence, in this case, no SR or BSR delay is assumed.
  • Scheme 6.4: Single CG configuration, where single PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. In this scheme no scheduling delay is assumed. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.5.1: Multiple CG configurations, where multiple PUSCH occasions per CG period are pre-configured with certain periodicity without relying on SR. In this scheme no scheduling delay is assumed. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.5.2: Multiple CG configurations, where multiple PUSCH occasions per CG period are pre-configured with certain periodicity without relying on SR. In this scheme scheduling delay for scheduling more packets with DG is assumed as 2.5 ms. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.6.1: Hybrid CG+DG scheduling - the scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with a certain size in UL slot in order to transmit BSR and data when a new XR packet arrives. Whenever a new XR packet arrives in the UE buffer, the UE uses the nearest possible CG PUSCH occasion for BSR transmission and possibly some amount of data. The network can thus use the BSR to provide dynamic grants for the following data transmission. CG periodicity and size of CG grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.6.2: Hybrid CG+DG scheduling - the scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with a certain size in order to transmit BSR only when a new XR packet arrives. It is assumed that one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets. Whenever a new XR packet arrives in the UE buffer, the UE uses the nearest possible CG PUSCH occasion for BSR transmission. The network can thus use the BSR to provide dynamic grants for the corresponding data scheduling. CG periodicity and size of CG grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.6.3: Hybrid CG+DG scheduling - the scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with a certain size in UL slot in order to transmit BSR and data when a new XR packet arrives. Whenever a new XR packet arrives in the UE's buffer, the UE uses the nearest possible CG PUSCH occasion for BSR transmission and possibly some amount of data. The network can thus use the BSR to provide dynamic grants for the following data transmission. The PDCCH monitoring window for the dynamic grant is pre-configured and associated with the CG PUSCH occasion in each CG period. The enhanced BSR that the BSR report will be triggered at the first used CG PUSCH occasion in each CG period to indicate to the gNB the remaining packet size is assumed. If the BSR is reported by the UE with the status "not empty", the UE would monitor PDCCH in the subsequent slots for dynamic grant after XR packet transmission with the CG resource, in which the dynamic grant is used to schedule the remaining data of XR packet. If the BSR is reported by the UE with the status "empty", the UE would not monitor PDCCH in the subsequent slots of the PDCCH monitoring window for XR packet transmission. Furthermore, if the XR packets are completely transmitted during the monitoring window, the UE can be indicated to go to sleep. If the XR packets arrive during the monitoring window, the UE can be indicated to skip the PDCCH monitoring until the packets arrive. CG periodicity and size of CG grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.7: Enhanced CG with flexible resource allocation, where at least one PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. In this scheme, it is assumed the UE can indicate to gNB unused CG PUSCH resources via CG-UCI. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.8: Enhanced CG with dynamic adaptation of CG parameters and indication of unused/used CG PUSCH occasion(s). In this scheme, the UE adjusts CG parameters dynamically: MCS, number of PRBs, number of layers within the CG resource. The UE indicates these scheduling parameters to the gNB via UCI transmitted separately in the same CG resource, and whether the subsequent CG PUSCH occasions will be used/unused until next XR packet arrival. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.9: Enhanced CG with indication of unused/used CG PUSCH occasion(s), where the UE only indicates if the subsequent CG PUSCH occasions will be used/unused until next XR packet arrival. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.10: Enhanced CG with MAC CE based dynamic resource adjustment indication. In this scheme, CG resource is used to carry MAC CE based dynamic resource adjustment indication and video data, and resource adjustment indication delay based on MAC CE is 2.5ms. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.11: Enhanced CG with UCI based dynamic resource adjustment indication. In this scheme, CG resource is used to carry UCI based dynamic resource adjustment indication and video data, and resource adjustment indication delay based on UCI is 0.5ms. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
  • Scheme 6.12: Enhanced CG with UCI based dynamic resource adjustment indication. In this scheme, CG resource is used to carry UCI based dynamic resource adjustment indication only, and the dynamic resource adjustment indication is used to inform the gNB data volume of an XR packet or required resources to transmit the XR packet. Resource adjustment indication delay based on UCI is 0.5ms. It is assumed that one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3.
Source Tdoc Source Scheme TDD format SU/MU-MIMO Data rate (Mbps) PDB (ms) Capa­city (UEs/cell) C1=floor (Capa­city) % of satis­fied UEs when #UEs/cell = C1 Notes
Source [CATT]R1-22111756.1.1DDDUUSU-MIMO10305.4590%Note 1,2,15
Source [CATT]R1-22111756.4*DDDUUSU-MIMO1030<10N.A.Note 1
Source [CATT]R1-22111756.6.3*DDDUUSU-MIMO10307.3791%Note 1,10,17
Source [CATT]R1-22111756.2*DDDUUSU-MIMO10307.2790%Note 1,13,16
Source [InterDigital]R1-22118436.1.1DDDSUSU-MIMO10307.1791%Note 1,2,12,18
1022100%
Source [InterDigital]R1-22118436.4**DDDSUSU-MIMO103066100%Note 1
104.7498%
Source [InterDigital]R1-22118436.7**DDDSUSU-MIMO10307.57100%Note 1
105.2599%
Source [vivo]R1-22125956.5.2***DDDSUSU-MIMO103011.31192.42%Note 1,7,14
106.22693.26%
Source [vivo]R1-22125956.10***DDDSUSU-MIMO103011.851193.46%Note 1,7
106.42694.44%
Source [vivo]R1-22125956.11***DDDSUSU-MIMO103012.871295.18%Note 1,7
107.81796.23%
Source [vivo]R1-22125956.6.2***DDDSUSU-MIMO103013.961394.08%Note 1,8,14
106.12692.13%
Source [vivo]R1-22125956.12***DDDSUSU-MIMO10108.79893.52%Note 1,8
Source [vivo]R1-22125956.5.2***DDDSUSU-MIMO10107.53794.41%Note 1,9,14
Source [vivo]R1-22125956.11***DDDSUSU-MIMO10108.83893.92%Note 1,9
Source [vivo]R1-22125956.1.1***DDDSUSU-MIMO103013.941393.96%Note 1,3,4,11,13
102.33295.69%
Source [vivo]R1-22125956.1.1***DDDSUSU-MIMO103013.821393.5%Note 1,5,6,11,14
1000N.A.
Source [vivo]R1-22125956.5.2***DDDUUSU-MIMO103013.411391.67%Note 1,7,14
1010.131094.18%
Source [vivo]R1-22125956.10***DDDUUSU-MIMO103013.851392.72%Note 1,7
1010.761094.61%
Source [vivo]R1-22125956.11***DDDUUSU-MIMO103014.941492.45%Note 1,7
1014.541493.07%
Source [vivo]R1-22125956.6.2***DDDUUSU-MIMO103016.731692.26%Note 1,8,14
106.57695.15%
Source [vivo]R1-22125956.1.1***DDDUUSU-MIMO103015.561593.42%Note 1,3,4,11,14
103.51393.24%
Source [vivo]R1-22125956.1.1***DDDUUSU-MIMO103015.21592.8%Note 1,5,6,11,14
1000N.A.
Source [vivo]R1-22125956.12***DDDUUSU-MIMO101010.321094.17%Note 1,8
Source [vivo]R1-22125956.5.2***DDDUUSU-MIMO101013.631392.46%Note 1,9,14
Source [vivo]R1-22125956.11***DDDUUSU-MIMO101015.151592.21%Note 1,9
NOTE 1:
BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1:4,4)
NOTE 2:
SR periodicity = 5 ms
NOTE 3:
SR delay = 3 ms
NOTE 4:
SR delay contains at least: delay for aligning to the nearest SR transmission occasion when an XR packet arrives, gNB processing delay for the reported SR.
NOTE 5:
SR delay = 5 ms
NOTE 6:
SR delay contains at least: delay for aligning to the nearest SR transmission occasion when an XR packet arrives, gNB processing delay for the reported SR.
NOTE 7:
Size of configured grant = 166.7 kbit, and the number of PUSCH occasions depends on some factors such as channel quality of the UE, and available resource, etc.
NOTE 8:
Size of configured grant = 80 bit
NOTE 9:
Size of configured grant = 83.4 kbit, and the number of PUSCH occasions depends on some factors such as channel quality of the UE, and available resource, etc.
NOTE 10:
Size of configured grant = 12096 bytes (128 PRBs with MCS 24)
NOTE 11:
Size of initial UL grant = 83.4 kbit
NOTE 12:
Size of initial UL grant = 400 kbits
NOTE 13:
Size of initial UL grant = 128 PRBs with dynamic MCS selection
NOTE 14:
BSR delay = 2.5 ms
NOTE 15:
Scheduling delay is 5 ms-15 ms
NOTE 16:
Scheduling delay is 0 ms-15 ms
NOTE 17:
Scheduling delay is 2 ms-15 ms
NOTE 18:
Scheduling delay = 5ms
*
CG periodicity = 16 ms
**
CG periodicity = 10 ms
***
CG periodicity pattern = (17,17,16) ms to align each CG occasion with a corresponding XR packet
Source Tdoc Source Scheme TDD format SU/MU-MIMO Data rate (Mbps) PDB (ms) Capa­city (UEs/cell) C1=floor (Capa­city) % of satis­fied UEs when #UEs/cell = C1 Notes
Source [Ericsson]R1-22109236.1.1DDDSUSU-MIMO10306.42692%Note 1,2,13,22
150.680N.A.
Source [Ericsson]R1-22109236.1.1DDDSUSU-MIMO10306.8695%Note 1,2,14,18,22
152.06290%
Source [Ericsson]R1-22109236.2DDDSUSU-MIMO10306.86695%Note 1,2,14,22
154.54493%
Source [Ericsson]R1-22109236.4*DDDSUSU-MIMO10306.35693%Note 1,2,10,19
6.4**152.75292%
Source [Ericsson]R1-22109236.6.1*DDDSUSU-MIMO10306.97695%Note 1,2,10,18,22
6.6.1**154.97494%
Source [Ericsson]R1-22109236.3DDDSUSU-MIMO10307.1791%Note 1,2
155.02590%
Source [Huawei]R1-22126506.1.1DDDSUMU-MIMO101000N.A.Note 1,3,15,18,24
Source [Huawei]R1-22126506.1.1DDDSUMU-MIMO101000N.A.Note 1,3,16,18,24
Source [Huawei]R1-22126506.2DDDSUMU-MIMO10101.7194.29%Note 1,15,16,19,24
Source [Huawei]R1-22126506.4***DDDSUMU-MIMO10101190.95%Note 1,12
Source [Huawei]R1-22126506.1.1DDDSUMU-MIMO101500N.A.Note 1,3,15,18,24
Source [Huawei]R1-22126506.1.1DDDSUMU-MIMO101500N.A.Note 1,3,16,18,20
Source [Huawei]R1-22126506.2DDDSUMU-MIMO1015>3396%Note 1,16,19,24
Source [Huawei]R1-22126506.6.1***DDDSUMU-MIMO101500N.A.Note 1,12,22
Source [Huawei]R1-22126506.5.2***DDDSUMU-MIMO10151.4197.14%Note 1,9,12,22
Source [Huawei]R1-22126506.9***DDDSUMU-MIMO10151.7198.57%Note 1,12,21,22
Source [Sony]R1-22116256.1.1DDDSUSU-MIMO101000N.A.Note 1,3,14,23
153390%
306.35691%
Source [Sony]R1-22116256.4**DDDSUSU-MIMO101000N.A.Note 1
Source [Sony]R1-22116256.8**DDDSUSU-MIMO10104490%Note 1,10,21
6.8**154.4492.5%Note 1,10,21
6.8*306.4696.5%Note 1,11,21
Source [Sony]R1-22116256.9**DDDSUSU-MIMO10101.6196%Note 1,10,21
6.9**153.25392.5%Note 1,10,21
6.9*306690%Note 1,11,21
Source [ZTE]R1-22119066.5.1****DDDSUSU-MIMO2030<10N.A.Note 1,4
15<10N.A.
10<10N.A.
Source [ZTE]R1-22119066.1.2DDDSUSU-MIMO20303.5194%Note 1,3,23
15<10N.A.
10<10N.A.
Source [ZTE]R1-22119066.1.1DDDSUSU-MIMO20303.6395%Note 1,3,17,22
152.1291%
10<10N.A.
Source [ZTE]R1-22119066.9****DDDSUSU-MIMO20303.9396%Note 1,5
153.5393%
102.6295%
Source [ZTE]R1-22119066.6.1****DDDSUSU-MIMO20303.7395%Note 1, 8, 11,22,25
152.1291%
10<10N.A.
Source [ZTE]R1-22119066.1.1DDDSUSU-MIMO20303.4393%Note 1,3,20,22
15<10N.A.
Source [ZTE]R1-22119066.6.1****DDDSUSU-MIMO20303.5393%Note 1,8,20,22,25
15<10N.A.
Source [ZTE]R1-22119066.5.1****DDDSUSU-MIMO1015<10N.A.Note 1,6
10<10N.A.
Source [ZTE]R1-22119066.1.2DDDSUSU-MIMO10154490%Note 1,3,23
10<10N.A.
Source [ZTE]R1-22119066.1.1DDDSUSU-MIMO10157790%Note 1,3,17,22
10<10N.A.
Source [ZTE]R1-22119066.9****DDDSUSU-MIMO10158.2891%Note 1,7
105.4591%
Source [ZTE]R1-22119066.6.1****DDDSUSU-MIMO10157.1791%Note 1,8, 11,22,25
NOTE 1:
64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8)
NOTE 2:
SR periodicity = 5ms
NOTE 3:
SR periodicity = 2.5 ms
NOTE 4:
10 CG configurations with single CG PUSCH in a period in each CG configuration
NOTE 5:
10 CG PUSCH in a period
NOTE 6:
8 CG configurations with single CG PUSCH in a period in each CG configuration
NOTE 7:
8 CG PUSCH in a period
NOTE 8:
Single CG PUSCH in a period
NOTE 9:
At least one PUSCH per CG occasion is pre-configured.
NOTE 10:
Size of configured grant = 60 kbit
NOTE 11:
Size of configured grant = 100 kbit
NOTE 12:
Size of configured grant is different for different UEs and it is up to configured resources and MCS
NOTE 13:
Size of initial UL grant = 288 bits
NOTE 14:
Size of initial UL grant = 117 kbit
NOTE 15:
Size of initial UL grant = 400 bits
NOTE 16:
Size of initial UL grant = 83.3 kbit
NOTE 17:
Size of initial UL grant is ideal at scheduler
NOTE 18:
No knowledge of XR traffic periodicity is assumed
NOTE 19:
It is assumed that the XR periodicity, frame size range and arrivals related information is known by gNB
NOTE 20:
BSR error probability is 10%
NOTE 21:
The indication of unused occasions was conveyed via new separate UCI
NOTE 22:
Scheduling delay is 2.5 ms
NOTE 23:
Scheduling delay is 5 ms
NOTE 24:
Scheduling delay is 2 slots
NOTE 25:
If CG occasion collides with DL slot due to CG periodicity equal to 16.5 ms, that particular CG occasion is not used.
*
CG periodicity = 5 ms
**
CG periodicity = 2.5 ms
***
CG periodicity pattern = (17,17,16) ms, the periodicities of packet arrival and CG PUSCH have been aligned
****
CG periodicity = 16.5 ms, the periodicities of packet arrival and the first CG PUSCH in each period have been aligned
Source Tdoc Source Scheme TDD format SU/MU-MIMO Data rate (Mbps) PDB (ms) Capa­city (UEs/cell) C1=floor (Capa­city) % of satis­fied UEs when #UEs/cell = C1 Notes
Source [vivo]R1-22125956.1.1DDDSUSU-MIMO0.210>30Note 1,2,4
Source [vivo]R1-22125956.1.1DDDSUSU-MIMO0.210>30Note 1,3,4
Source [vivo]R1-22125956.4*DDDSUSU-MIMO0.210>30Note 1
NOTE 1:
BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1:4,4)
NOTE 2:
SR delay = 3 ms
NOTE 3:
SR delay = 5 ms
NOTE 4:
Size of initial UL grant = 100 bytes
*
CG periodicity = 5 ms
Based on the evaluation results in Table B.1.6-1, Table B.1.6-2 the following observations can be made:
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.42 UEs per cell with DG scheduling with SR followed by small initial UL grant (288 bits) with BSR and data (scheme 6.1.1) to 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 7%). The capacity gain for 15ms PDB is 567%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.8 UEs per cell with DG scheduling with SR followed by large initial UL grant (117 kbit) with BSR and data (scheme 6.1.1) to 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 1%). The capacity gain for 15ms PDB is 120%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is decreased from 6.42 UEs per cell with DG scheduling with SR followed by small initial UL grant (288 bits) with BSR and data (scheme 6.1.1) to 6.35 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -1%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is decreased from 6.8 UEs per cell with DG scheduling with SR followed by large initial UL grant (117 kbit) with BSR and data (scheme 6.1.1) to 6.35 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -7%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 0.68 UEs per cell with DG scheduling with SR followed by small initial UL grant (288 bits) with BSR and data (scheme 6.1.1) to 2.75 UEs per cell with single CG configuration (scheme 6.4) (capacity gain is 304%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 2.06 UEs per cell with DG scheduling with SR followed by large initial UL grant (117 kbit) with BSR and data (scheme 6.1.1) to 2.75 UEs per cell with single CG configuration (scheme 6.4) (capacity gain is 33%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.35 UEs per cell with single CG configuration (scheme 6.4) to 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 8%). The capacity gain for 15ms PDB is 65%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.35 UEs per cell with single CG configuration (scheme 6.4) to 6.97 UEs per cell with hybrid scheduling CG+DG, where CG resources are configured with a certain size in every UL slot in order to transmit BSR and data when new data arrives (scheme 6.6.1) (capacity gain is 10%). The capacity gain for 15ms PDB is 81%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) to 6.97 UEs per cell with hybrid scheduling CG+DG, where CG resources are configured with a certain size in every UL slot in order to transmit BSR and data when new data arrives (scheme 6.6.1) (capacity gain is 2%). The capacity gain for 15ms PDB is 9%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.97 UEs per cell with hybrid scheduling CG+DG, where CG resources are configured with a certain size in every UL slot in order to transmit BSR and data when new data arrives (scheme 6.6.1) to 7.1 UEs per cell with dynamic scheduling with genie BSR (scheme 6.3) (capacity gain is 2%). The capacity gain for 15ms PDB is 1%.
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is decreased from 7.1 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -15%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 2 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 4.7 UEs per cell with single CG configuration (scheme 6.4) (capacity gain is 135%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 7.1 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 7.5 UEs per cell with enhanced CG with flexible resource allocation (scheme 6.7) (capacity gain is 6%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 2 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 5.2 UEs per cell with enhanced CG with flexible resource allocation (scheme 6.7) (capacity gain is 160%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is decreased from 5.4 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 0 UEs per cell with single CG configuration (scheme 6.4).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is increased from 5.4 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 7.3 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.3) (capacity gain is 35%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is increased from 5.4 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 7.2 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 33%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is decreased from 6.35 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 5.6 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -11%). The capacity drop for 15ms PDB is 17%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is increased from 6.35 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6.4 UEs per cell with enhanced CG with dynamic adaptation of CG parameters and indication of unused/used CG PUSCH occasion(s) (scheme 6.8) (capacity gain is 1%). The capacity gain for 15ms PDB is 44%.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is decreased from 6.35 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity drop is -6%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is increased from 3 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 3.25 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 8%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.5 UEs per cell with DG scheduling with SR followed by UL grant with BSR only (scheme 6.1.2) to 3.6 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) (capacity gain is 3%). The trend is similar for PDB=10 ms and 15 ms as well as for 10Mbps scenario.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is decreased from 3.6 UEs per cell with DG scheduling with SR followed by UL grant with BSR and data (scheme 6.1.1) to 0 UEs per cell with multiple CG configurations (scheme 6.5.1). The trend is similar for PDB=10 ms and 15 ms as well as for 10Mbps scenario.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.6 UEs per cell with DG scheduling with SR followed by UL grant with BSR and data (scheme 6.1.1) to 3.9 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 8%). The trend is similar if compare (scheme 6.1.2) with (scheme 6.9).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 2.1 UEs per cell (scheme 6.1.1) to 3.5 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 66.7%). The trend is similar if compare (scheme 6.9) with (scheme 6.1.2) or (scheme 6.6.1) for PDB=15 ms and for 20Mbps scenario.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 7 UEs per cell (scheme 6.1.1) to 8.2 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 17%). The trend is similar if compare (scheme 6.9) with (scheme 6.6.1) for PDB=15 ms and for 10Mbps scenario.
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 10ms PDB, 60FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 0 UE per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 1.1) to 2.6 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 9). The trend is similar if compare (scheme 1.2) with (scheme 9).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.7 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.1) to 3.9 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 5%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 4 UEs per cell (scheme 6.1.2) to 8.2 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 95.2%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.5 UEs per cell (scheme 6.6.1) assuming 10% BSR error probability to 3.9 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 11.4%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 2.33 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6.22 UEs per cell with multiple CG configurations (scheme 6.5.2) (capacity gain is 167%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 2.33 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) (capacity gain is 163%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) to 6.42 UEs per cell with enhanced CG with MAC CE based dynamic resource adjustment indication (scheme 6.10) (capacity gain is 5%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) to 7.81 UEs per cell with enhanced CG with UCI based dynamic resource adjustment indication (scheme 6.11) (capacity gain is 28%).
  • For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) to 8.79 UEs per cell with enhanced CG with UCI based dynamic resource adjustment indication (scheme 6.12) (capacity gain is 44%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by small initial UL grant (400 bits) with BSR and data (scheme 6.1.1) to 1 UE per cell with single CG configuration (scheme 6.4).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by large initial UL grant (83.3 kbit) with BSR and data (scheme 6.1.1) to 1 UE per cell with single CG configuration (scheme 6.4).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 1 UE per cell with cell with single CG configuration (scheme 6.4) to 1.7 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 70%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by small initial UL grant (400 bits) with BSR and data (scheme 6.1.1) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by large initial UL grant (83.3 kbit) with BSR and data (scheme 6.1.1) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 1.4 UEs per cell with multiple CG configuration (scheme 6.5.2) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 21%).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.1) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9).
  • For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is decreased from 3 UEs per cell with cell with pre-scheduling dynamic grant (scheme 6.2) to 1.7 UEs per cell with Enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity drop is -43%).
Up

Up   Top   ToC