1. 14 Feb, 2016 1 commit
  2. 11 Feb, 2016 1 commit
  3. 01 Feb, 2016 1 commit
  4. 21 Jan, 2016 1 commit
  5. 12 Jan, 2016 1 commit
  6. 08 Jan, 2016 2 commits
  7. 07 Jan, 2016 2 commits
  8. 06 Jan, 2016 2 commits
  9. 31 Dec, 2015 1 commit
  10. 29 Dec, 2015 2 commits
  11. 22 Dec, 2015 1 commit
  12. 21 Dec, 2015 1 commit
  13. 17 Dec, 2015 1 commit
  14. 14 Dec, 2015 1 commit
  15. 05 Dec, 2015 1 commit
  16. 04 Dec, 2015 1 commit
  17. 29 Nov, 2015 1 commit
  18. 25 Nov, 2015 1 commit
  19. 24 Nov, 2015 4 commits
  20. 23 Nov, 2015 1 commit
    • 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
  21. 19 Nov, 2015 2 commits
  22. 18 Nov, 2015 2 commits
  23. 10 Nov, 2015 2 commits
    • 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
  24. 28 Oct, 2015 2 commits
  25. 26 Oct, 2015 2 commits
  26. 22 Oct, 2015 1 commit
  27. 20 Oct, 2015 1 commit
  28. 19 Oct, 2015 1 commit