Describe the bug
Currently, the number of PRBs needed for a UE in DL is calculated at the scheduler level based on the current queue size of the UE.
This, however generates some misunderstanding in full buffer scenarios due to the overhead and the rate matching at the creation of the TB.
To Reproduce
Steps to reproduce the behavior:
Run a simulation with the traffic profile set to fullBuffer and notice the size extracted from the queue at scheduling time and what ends up being the data payload in the TB.
Expected behavior
A possible solution is to account for the TB overhead at the moment of the selection of the number of PRBs needed by a UE at scheduler level. This way the queue extraction accounts only for the data payload of the TB, while the number of PRBs allocated is based on the overall size of the TB including the overhead
Describe the bug Currently, the number of PRBs needed for a UE in DL is calculated at the scheduler level based on the current queue size of the UE. This, however generates some misunderstanding in full buffer scenarios due to the overhead and the rate matching at the creation of the TB.
To Reproduce Steps to reproduce the behavior: Run a simulation with the traffic profile set to fullBuffer and notice the size extracted from the queue at scheduling time and what ends up being the data payload in the TB.
Expected behavior A possible solution is to account for the TB overhead at the moment of the selection of the number of PRBs needed by a UE at scheduler level. This way the queue extraction accounts only for the data payload of the TB, while the number of PRBs allocated is based on the overall size of the TB including the overhead