dear author
Does simu5G support numerologyIndex =2, 3, 4 in dual connection scenarios.
I configured the index to 4.
*.carrierAggregation.componentCarrier[1].numerologyIndex=4
But I observe the resource scheduling of each MAC,
time0.0020625ue2049Bytes13662blocks54
time0.002125ue2049Bytes4554blocks18
time0.002625ue2049Bytes4554blocks18
time0.0031875ue2049Bytes4554blocks18
time0.0036875ue2049Bytes4554blocks18
time0.0041875ue2049Bytes4554blocks18
time0.0046875ue2049Bytes4554blocks18
time0.0105625ue2049Bytes4554blocks18
time0.0110625ue2049Bytes4554blocks18
time0.0115625ue2049Bytes4554blocks18
time0.012125ue2049Bytes4554blocks18
I found that the interval is 0.5ms, why is the interval not equal to one TTI, which is 0.065ms?
And I set the numerologyIndex to 2, 3, and 4, with intervals of 0.5ms.
dear author Does simu5G support numerologyIndex =2, 3, 4 in dual connection scenarios.
I configured the index to 4. *.carrierAggregation.componentCarrier[1].numerologyIndex=4
But I observe the resource scheduling of each MAC, time0.0020625ue2049Bytes13662blocks54 time0.002125ue2049Bytes4554blocks18 time0.002625ue2049Bytes4554blocks18 time0.0031875ue2049Bytes4554blocks18 time0.0036875ue2049Bytes4554blocks18 time0.0041875ue2049Bytes4554blocks18 time0.0046875ue2049Bytes4554blocks18 time0.0105625ue2049Bytes4554blocks18 time0.0110625ue2049Bytes4554blocks18 time0.0115625ue2049Bytes4554blocks18 time0.012125ue2049Bytes4554blocks18
I found that the interval is 0.5ms, why is the interval not equal to one TTI, which is 0.065ms? And I set the numerologyIndex to 2, 3, and 4, with intervals of 0.5ms.
thanks!