Skip to content

Avoid saturation in PUSCH for UL channel estimation

Roberto Louro Magueta requested to merge develop-UL-saturation into develop

Tests with USRPs and COTS UE showed that the 2-layer UL was failing, because the received signal was very strength, and consequently there was saturation. Therefore, this MR:

  • Avoid saturation in PUSCH for UL channel estimation, checking the strength of the received signal;
  • Remove the procedures to improve the channel estimates around DC, because new filters have recently been applied, and this procedure is no longer necessary.

The main results with USRPs and COTS UE, using cables, show that:

  • Up to MCS=12, 2-layer UL is quite stable, even doing iPerf;
UE RNTI 3bc3 (1) PH 60 dB PCMAX 21 dBm, average RSRP -61 (16 meas)
UE 3bc3: CQI 0, RI 1, PMI (0,0)
UE 3bc3: UL-RI 2, TPMI 0
UE 3bc3: dlsch_rounds 11407/1/1/0, dlsch_errors 0, pucch0_DTX 2, BLER 0.00000 MCS 9
UE 3bc3: dlsch_total_bytes 2474289
UE 3bc3: ulsch_rounds 203040/18/3/3, ulsch_DTX 12, ulsch_errors 3, BLER 0.00000 MCS 12
UE 3bc3: ulsch_total_bytes_scheduled 435073073, ulsch_total_bytes_received 435066159
UE 3bc3: LCID 1: 1575 bytes TX
UE 3bc3: LCID 4: 23630 bytes TX
UE 3bc3: LCID 4: 432313564 bytes RX
[  3] 300.0-301.0 sec  1.23 MBytes  10.3 Mbits/sec   4.393 ms    0/  878 (0%)
[  3] 301.0-302.0 sec  1.23 MBytes  10.3 Mbits/sec   1.748 ms    0/  878 (0%)
[  3] 302.0-303.0 sec  1.23 MBytes  10.3 Mbits/sec   5.252 ms    0/  878 (0%)
[  3] 303.0-304.0 sec  1.23 MBytes  10.3 Mbits/sec  11.939 ms    0/  878 (0%)
[  3] 304.0-305.0 sec  1.23 MBytes  10.3 Mbits/sec   1.257 ms    0/  878 (0%)
[  3] 305.0-306.0 sec  1.23 MBytes  10.3 Mbits/sec   1.798 ms    0/  878 (0%)
[  3] 306.0-307.0 sec  1.23 MBytes  10.3 Mbits/sec   1.208 ms    0/  878 (0%)
[  3] 307.0-308.0 sec  1.23 MBytes  10.3 Mbits/sec   4.620 ms    0/  878 (0%)
[  3] 308.0-309.0 sec  1.23 MBytes  10.3 Mbits/sec   1.734 ms    0/  878 (0%)
[  3] 309.0-310.0 sec  1.23 MBytes  10.3 Mbits/sec   7.213 ms    0/  879 (0%)
[  3] 310.0-311.0 sec  1.23 MBytes  10.3 Mbits/sec   1.226 ms    0/  878 (0%)
[  3] 311.0-312.0 sec  1.23 MBytes  10.3 Mbits/sec   1.229 ms    0/  878 (0%)
[  3] 312.0-313.0 sec  1.23 MBytes  10.3 Mbits/sec   1.248 ms    0/  878 (0%)
  • It works up to MCS=28, but the performance is still not good enough to do iPerf.
UE RNTI 58ff (1) PH 50 dB PCMAX 21 dBm, average RSRP -61 (16 meas)
UE 58ff: CQI 0, RI 1, PMI (0,0)
UE 58ff: UL-RI 2, TPMI 0
UE 58ff: dlsch_rounds 15561/2/1/0, dlsch_errors 0, pucch0_DTX 2, BLER 0.00000 MCS 9
UE 58ff: dlsch_total_bytes 3375707
UE 58ff: ulsch_rounds 424104/73/21/3, ulsch_DTX 12, ulsch_errors 3, BLER 0.00000 MCS 28
UE 58ff: ulsch_total_bytes_scheduled 72913302, ulsch_total_bytes_received 72912580
UE 58ff: LCID 1: 4692 bytes TX
UE 58ff: LCID 4: 1187 bytes TX
UE 58ff: LCID 4: 13021 bytes RX

Merge request reports