1. 04 Sep, 2018 1 commit
  2. 30 Jul, 2018 3 commits
  3. 05 Jul, 2018 1 commit
  4. 29 Jun, 2018 1 commit
  5. 27 Jun, 2018 1 commit
  6. 25 Jun, 2018 1 commit
  7. 03 Jun, 2018 1 commit
  8. 02 Jun, 2018 1 commit
  9. 10 May, 2018 1 commit
  10. 29 Apr, 2018 1 commit
  11. 25 Apr, 2018 1 commit
  12. 23 Apr, 2018 3 commits
  13. 22 Apr, 2018 1 commit
  14. 20 Apr, 2018 1 commit
  15. 19 Apr, 2018 2 commits
  16. 16 Apr, 2018 1 commit
    • Bi-Ruei, Chiu's avatar
      Compare version number using MAKE_VERSION macro to provide better SW configuration: · 5c23af77
      Bi-Ruei, Chiu authored
      1. Previous SW configuration for different RRC version relies on whether macro Rel10,
         Rel14 defined or not by checking #ifdef Rel14 or #if defined(Rel10) || defined(R14).
         Whenever there is a newer RRC version, e.g. Rel15, it will be very a tedious and
         error-prone job to add defined(Rel15) in every place.
      
      2. Some RRC messages are defined in release 13 instead of release 14, NB-IoT
         feature is one of such example. Our code shall reflect this fact instead of using
         an afterward version number in software configuration.
      
      3. Some RRC messages or some fields of certain RRC messages are added in the middle
         a release, e.g. SystemInformationBlockType1_v1310_IEs_t defined in RRC 13.1.0
         and RRC 9.2.0 made some changes to SIB12 and SIB13 so we have sib12_v920 and
         sib13_v920 fields in SIB12 and SIB13's struct.
         We need a finer grain of control when using ASN1 from different RRC version.
      
      4. S1AP also has this problem that it use UPDATE_RELEASE_9 and UPDATE_RELEASE_10 to
         differentiate between various S1AP version.
      
      This commit propose using MAKE_VERSION(x,y,z) to designate the version number and
      modify current conditional compilation accordingly.
      
      Note: 2018/04/16, Modified based on Cedric's comment.
      5c23af77
  17. 15 Mar, 2018 1 commit
  18. 01 Mar, 2018 1 commit
  19. 26 Feb, 2018 2 commits
  20. 24 Feb, 2018 1 commit
  21. 22 Feb, 2018 2 commits
  22. 20 Feb, 2018 1 commit
  23. 19 Feb, 2018 2 commits
  24. 12 Feb, 2018 2 commits
  25. 07 Feb, 2018 2 commits
    • Cedric Roux's avatar
      bugfix: don't take into account report CQI in case of NACK or DTX · c0bcd786
      Cedric Roux authored
      The problem that may happen is that when the UE does not transmit
      on PUCCH (for whatever reason) we may get no signal at all, and
      thus compute a very low CQI. Later on we may ask the UE to transmit
      louder which may lead to saturation and more problems.
      
      The solution is simple: don't care about CQI in case of DTX
      (and NACK also, as done for PUSCH).
      
      Only FDD case done.
      For TDD it seems that:
      - nfapi structures are not correct. See nfapi_harq_indication_tdd_rel13_t
        in nfapi/open-nFAPI/nfapi/public_inc/nfapi_interface.h, all the cases
        (bundling, multiplex, ...) use nfapi_harq_indication_tdd_harq_data_t
      - the function extract_harq does not handle TDD
      c0bcd786
    • Cedric Roux's avatar
      minor: fix AssertFatal · 9b7364a3
      Cedric Roux authored
      9b7364a3
  26. 06 Feb, 2018 3 commits
  27. 05 Feb, 2018 2 commits