1. 06 Dec, 2016 1 commit
  2. 05 Dec, 2016 1 commit
  3. 29 Nov, 2016 1 commit
  4. 28 Nov, 2016 6 commits
  5. 24 Nov, 2016 8 commits
  6. 21 Nov, 2016 4 commits
  7. 18 Nov, 2016 5 commits
    • knopp's avatar
    • Gabriel's avatar
      BSR fixes for ping · 7f740654
      Gabriel authored
    • Cédric Roux's avatar
      T: add a trace for PHICH · c03f13c0
      Cédric Roux authored
    • calvin wang's avatar
      fix bsr report inaccurate value · 319ae6fb
      calvin wang authored
    • Cédric Roux's avatar
      hotfix: correct PHICH generation · 64615dcc
      Cédric Roux authored
      The PHICH generation is wrong.
      HARQ process X is uplink scheduled at TTI n.
      At TTI n+4 the eNB receives the data.
      At TTI n+8 the eNB sends ACK/NACK on the PHICH.
      The problem is that PHICH generation is done after scheduling.
      And PHICH generation uses "first_rb" and "n_DMRS" to compute
      "ngroup_PHICH" and "nseq_PHICH".
      So at TTI n+8 if the eNB has reused the HARQ process X for
      a new uplink scheduling the values "first_rb" and "n_DMRS"
      may have changed.
      We need to use the previous values.
      One solution would have been to do PHICH generation before
      scheduling. The problem is that "generate_phich_top" does more
      than PHICH generation. It has to setup parameters to sort of
      "emulate" a DCI0 in case of retransmission scheduled without
      DCI0. So part of it has to be done after scheduling. We would
      have to split the function.
      The simple adopted fix is to store old values of "first_rb"
      and "n_DMRS" and use those values in "generate_phich_top".
      This fix has only been tested with FDD. TDD may miserably fail.
  8. 16 Nov, 2016 4 commits
  9. 15 Nov, 2016 3 commits
  10. 14 Nov, 2016 3 commits
  11. 11 Nov, 2016 1 commit
  12. 10 Nov, 2016 3 commits