Did yall get answers to your questions? I have similar questions. It will be very helpful if you can share your experience and insights.
The first thing is the document does not show what is the unit of the size of TB in the trace files. Is it byte? Hope someone can clarify that.
And, it seems NS3 is using a burst of packets to simulate the table 7.1.7.2.1-1 in 3gpp 36.213.
The model of the MAC Transport Blocks (TBs) provided by the simulator is simplified with respect to the 3GPP specifications. In particular, a simulator-specific class (PacketBurst) is used to aggregate MAC SDUs in order to achieve the simulator’s equivalent of a TB, without the corresponding implementation complexity. The multiplexing of different logical channels to and from the RLC layer is performed using a dedicated packet tag (LteRadioBearerTag), which performs a functionality which is partially equivalent to that of the MAC headers specified by 3GPP.
(what is SDU size and the number SDUs? is the TB size in the trace actually SDU size? asking this because I found the TB size in the trace is too small comparing the goodput results)
However, it seems the tbSize in the program and trace mean a different thing as in the 3gpp 36.213? We need to time the value of TB size in the trace file (2196 for one user really close to enb) with the number of packets? Based on this one post, we need to time it by 4?