Skip to content
Snippets Groups Projects
Select Git revision
  • develop default
  • 2023.w43
  • 2023.w42
  • 2023.w41
  • 2023.w40
  • 2023.w39
  • 2023.w38
  • 2023.w37
  • 2023.w36
  • 2023.w34
  • 2023.w33
  • 2023.w32
  • v2.0.0
  • 2023.w31
  • 2023.w30
  • 2023.w29
  • 2023.w28
  • 2023.w27
  • 2023.w26
  • 2023.w25
  • 2023.w24
21 results
Search by author
  • Any Author
  • Pablo Andres Vazquez Saravia Pablo Andres Vazquez Saravia pablo.vazquez
  • Walter Angel Piastri Ferreira Walter Angel Piastri Ferreira walter.piastri
  • Wilder Fabian Peña Tremezana Wilder Fabian Peña Tremezana wilder.pena
3 authors
  1. Dec 29, 2015
  3. Dec 04, 2015
  5. Nov 23, 2015
    • Cedric Roux's avatar
      Manage free downlink HARQ processes with a circular list. · f14a401f
      Cedric Roux authored 
      The oldest PID (the PID that was used the longest
TTI ago) is at the head and is the next one that
will be used.

No test is done to check that when a process is
allocated it is at least N TTIs old, but some quick
thinking strongly leads to the 'conclusion' that N
won't be smaller than 8, which seems to be what
cat3 UEs require to function properly in the downlink
direction (from the eNodeB to the UE).
      f14a401f
  7. Nov 18, 2015
  9. Nov 10, 2015
    • Cedric Roux's avatar
      Give a better name to this array. · 68249569
      Cedric Roux authored
      68249569
    • Cedric Roux's avatar
      This is a very basic fix, more work is needed. · f2b3597b
      Cedric Roux authored 
      The problem seems that we reuse HARQ processes too early.
For example, at subframe 0 we allocate PID 0. At subframe 4
we receive an ACK. At subframe 5 we may well reallocate this
PID. It seems category 3 UEs don't like that. They expect
some delay. How much? I don't know. 8 maybe, as for UL.

This commit forces allocation of HARQ PID:
  0 on subframe 1,
  1 on subframe 2,
  2 on subframe 3,
  3 on subframe 4,
  4 on subframe 6,
  5 on subframe 7,
  6 on subframe 8,
  7 on subframe 9.

We don't use subframes 0 and 5 (for initial transmission at
least). (Current develop branch doesn't either I think.)

This is not a good solution, just a quick and dirty one. With this
commit I can achieve 12Mbps with iperf UDP on a 5MHz band 7 carrier
with a cat3 UE. And more than 11Mbps with iperf TCP. And a bad
radio link.

We may want to implement some sort of free-list and take the
oldest PID in there, if it is older than let's say 8 subframes
(that is: the last transmission with this pid was done more
than 8 subframes ealier). We may well have no free PID if a
lot of retransmissions are done.
      f2b3597b
  11. Oct 28, 2015
  13. Oct 26, 2015
  15. Oct 20, 2015
  17. Oct 15, 2015
  19. Oct 13, 2015
  21. Oct 12, 2015
  23. Oct 06, 2015
  25. Oct 02, 2015
  27. Oct 01, 2015
  29. Sep 30, 2015
  31. Sep 28, 2015
  33. Sep 21, 2015
  35. Sep 19, 2015
  37. Sep 10, 2015
  39. Sep 09, 2015
  41. Sep 08, 2015
  43. Sep 07, 2015
  45. Sep 04, 2015
  47. Sep 03, 2015
  49. Sep 02, 2015
  51. Sep 01, 2015
  53. Aug 19, 2015
  55. Aug 07, 2015
  57. Jul 28, 2015
  59. Jul 26, 2015