1. 22 Nov, 2016 5 commits
    • Cédric Roux's avatar
      T: update a trace · b526ef7b
      Cédric Roux authored
      add ndi to trace ENB_MAC_UE_DL_SDU
    • Cédric Roux's avatar
      T: fix small typo · 3ae5f956
      Cédric Roux authored
    • Cédric Roux's avatar
      hotfix: hack to improve PHICH generation · b55b63c5
      Cédric Roux authored
      The eNodeB may sometimes wrongly generate PHICH because somewhere
      'phich_active' is not reset to 0, due to an unidentified reason. When
      adding this hack the problem seems to disappear completely.
      This is not the end of the story. The real underlying problem has to be
      understood and fixed correctly.
    • Cédric Roux's avatar
      hotfix: correct Msg3 ressource blocks reservation · 6bb69e19
      Cédric Roux authored
      The Msg3 ressource blocks used by random access procedure
      were not correctly handled. The MAC scheduler could wrongly
      allocate a ressource block for both random access Msg3 and
      a regular UE.
      This hotfix hopefully fixes the problem.
      A new function "set_msg3_subframe" has been added in the
      interface between PHY and MAC.
    • Cédric Roux's avatar
      T: add some traces · 43df2913
      Cédric Roux authored
      - Msg3 allocation
      - initiation of Random Access procedure
  2. 18 Nov, 2016 3 commits
    • knopp's avatar
    • Cédric Roux's avatar
      T: add a trace for PHICH · c03f13c0
      Cédric Roux 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.
  3. 16 Nov, 2016 1 commit
    • Cédric Roux's avatar
      hotfix: turbo decoder should not fail if CRC is 0 · f116a10d
      Cédric Roux authored
      The case of a CRC == 0 is legal.
      After discussion with Raymond, it is also possible to have all
      bits at 0 (and so a CRC==0) if there is no transmission and thus
      not much energy.
      So this hotfix may introduce new problems (false decoding).
      A future work is to handle this case properly by not calling the
      turbo decoder if there is not enough energy received.
      The problem might manifest itself more in the UE part, especially
      when it tries to decode MIB and/or SIB (if I understood correctly).
  4. 14 Nov, 2016 2 commits
  5. 10 Nov, 2016 3 commits
  6. 08 Nov, 2016 1 commit
  7. 04 Nov, 2016 1 commit
  8. 03 Nov, 2016 5 commits
  9. 25 Oct, 2016 2 commits
  10. 21 Oct, 2016 1 commit
  11. 19 Oct, 2016 1 commit
  12. 18 Oct, 2016 2 commits
  13. 17 Oct, 2016 4 commits
  14. 13 Oct, 2016 1 commit
  15. 12 Oct, 2016 3 commits
  16. 11 Oct, 2016 5 commits