1. 12 Dec, 2016 4 commits
  2. 08 Dec, 2016 3 commits
  3. 05 Dec, 2016 1 commit
  4. 30 Nov, 2016 1 commit
    • Cedric Roux's avatar
      T: update traces · 7adc4703
      Cedric Roux authored
      - add mcs to ENB_PHY_DLSCH_UE_DCI
      - add mcs, round, first_rb, nb_rb, TBS to ENB_PHY_ULSCH_UE_DCI
  5. 28 Nov, 2016 1 commit
  6. 25 Nov, 2016 1 commit
  7. 24 Nov, 2016 3 commits
  8. 22 Nov, 2016 6 commits
  9. 21 Nov, 2016 1 commit
    • Gabriel's avatar
      [OAI-UE] several fixes in OAI-UE · 9c4cee34
      Gabriel authored
                 1- implement max harq retrans
                 2- bug in harqId > 1 for dci format 1A
                 3- wrong G computation
                 4- bug in harq UL for scheduling flag
                 5- initial sync, limit freq offset to 150Hz
  10. 18 Nov, 2016 4 commits
    • knopp's avatar
    • ROBERT Benoit's avatar
      Add following functionnalities to OAI UE autotest framework · 0b1050c1
      ROBERT Benoit authored
      - add progess bar report
      - reduce ssh max_tries to 10
      - cleanOldPrograms -> change kill cmd line to be able to run autotest on same machine than lte-softmodem (thanks Rohit & Gabriel)
      - Cleanning output prints
      - add --skip-machine-preparation on cmd line
      - add --skip-sanity-check on cmd line
      - add HTML REPORT (no-S1 only)
      - add XML detailled report (no-S1 only)
    • Cedric Roux's avatar
      T: add a trace for PHICH · c03f13c0
      Cedric Roux authored
    • Cedric Roux's avatar
      hotfix: correct PHICH generation · 64615dcc
      Cedric 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.
  11. 16 Nov, 2016 1 commit
    • Cedric Roux's avatar
      hotfix: turbo decoder should not fail if CRC is 0 · f116a10d
      Cedric 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).
  12. 09 Nov, 2016 2 commits
  13. 07 Nov, 2016 2 commits
  14. 04 Nov, 2016 2 commits
  15. 25 Oct, 2016 1 commit
  16. 20 Oct, 2016 1 commit
  17. 18 Oct, 2016 1 commit
    • fnabet's avatar
      [OAI-UE] SRS feature · 9938bd5d
      fnabet authored
                         1- Implement SRS procedures
                         2- Implement SRS procedures part2
                         3- Implement SRS: SRS valid on CMW
  18. 12 Oct, 2016 2 commits
  19. 10 Oct, 2016 2 commits
    • Cedric Roux's avatar
      issue 137 - fix RI bits decoding · 190fc96a
      Cedric Roux authored
      RI bits are present only in some transmission modes.
      For aperiodic reporting (the mode we do as of today),
      36.213 7.2.1 (release 10) says:
          "RI is only reported for transmission modes 3 and 4,
          as well as transmission modes 8 and 9 with PMI/RI reporting"
      This commit activates decoding of RI bits only for transmission
      modes 3 and 4. 8 and 9 are not done today (as far as I know).
    • Cedric Roux's avatar
      issue 137 - correct computation of G · b0887a1b
      Cedric Roux authored
      G was wrongly computed in some places, not taking into account
      CQI and RI bits. This commit saves the correct value computed
      in ulsch_decoding so we can reuse it in ulsch_decoding_data
      (and the like).
      Only the file openair1/PHY/LTE_TRANSPORT/ulsch_decoding.c has
      been checked. If the computation is done somewhere else the
      problem might still exist.
  20. 09 Oct, 2016 1 commit