search

Unipisa / Simu5G

Simu5G - 5G NR and LTE/LTE-A user-plane simulation model for OMNeT++ & INET
https://simu5g.org
Other
146 stars 83 forks source link

Is there a macCellThroughputDl measurement error? #66

Closed hullopes closed 2 years ago

hullopes commented 2 years ago

Hi there. Running the /simu5G/simulations/NR/standalone_multicell/omnetpp.ini with different .carrierAggregation.componentCarrier[].numBands values, I expected to see higher throughput values increasing the bandwidth (6 to 50, e.g.), but I see in the results something strange. For instance: for: .carrierAggregation.componentCarrier[].numBands = 6 we get scalar MultiCell_Standalone.gnb1.cellularNic.mac macCellThroughputDl:mean 58152.100614993

for: .carrierAggregation.componentCarrier[].numBands = 100 we get scalar MultiCell_Standalone.gnb1.cellularNic.mac macCellThroughputDl:mean 58082.317802289

giovanninardini commented 2 years ago

Hello,

the numBands parameter changes the available bandwidth provided by the cell (number of RBs). The macCellThroughput statistic measures the total traffic that the cell was able to serve. This metric depends on the traffic generated by the UEs and on the number of available bands, but only if the traffic was so high that the available bands were not enough to serve all the traffic generated by the UEs. For example, if the traffic generated by the UEs only occupies 3 RBs, then the macCellThroughput statistic will not change by increasing the numBands parameter from 6 to 100, since the UEs will still occupy 3 RBs only. You can observe the avgServedBlocks metric to see how many bands, on average, were allocated.

hullopes commented 2 years ago

Thank you very much.