The discard timer is used by the PDCP layer to discard packets that were not
transmitted to RLC after some time.
We don't really need it for the moment, maybe never for the default
bearer which is a best-effort bearer passing all kind of IP traffic.
Maybe for voice over IP kind of traffic it's important, or realtime
applications.
I ran an iperf UDP uplink test and saw no error on the PHY layer but still
lots of packets lost in the iperf logs, which was very surprising. By
analyzing the logs in wireshark I saw that, with the current scheduler,
an IP packet sent by the UE took 40ms to be sent piece by piece to the
gNB, and then the next uplink IP packet was never sent at all because
the discard timer was expired, leading to the high count of packets lost
in the iperf logs.
So let's put infinity for the moment for the discard timer. From my
understanding of the moment it's not a problem. If for some reason we
should set it to some non-infinity value, then we can change later.
- FAPI structures not to be used as config_req at MAC since that FAPI is
just for communication between MAC and PHY
- additional frame_type member added to the FAPI struct
- currently, -25 dBm/RE is the maximum measured power from USRP
corresponding to att_tx = 0 dB, therefore ssPBCH_BlockPower has been
updated accordingly
- this param is used at UE side for the pathloss computation, which now
seems to match measurements observed during lab testing
- new function has been introduced for the computation of UL SNR
- minor bugfix to noise power computation
- FAPI data type for referenceSignalPower has been updated to reflect the
range of values for the SSB power
- pathloss, RSSI, RSRP and Noise measurements have been reviewed and wrong
implementation has been fixed
- referenceSignalPower type in the FAPI struct has been changed to int
has its range include negative values
masayuki.harada