1. 19 Mar, 2018 1 commit
    • Cedric Roux's avatar
      bugfix: send UL NACK (on PHICH) at the right place · d3938147
      Cedric Roux authored
      The PHICH was not programmed for the last round (4) because it was
      not programmed in rx_sdu but in schedule_ulsch_rnti, only in case
      of a programmed retransmission (there is obviously no retransmission
      programmed after the last round).
      
      The case of Msg3 is not handled. To be done somehow.
      d3938147
  2. 15 Mar, 2018 1 commit
  3. 09 Mar, 2018 2 commits
  4. 08 Mar, 2018 2 commits
    • oai's avatar
      more NB-IoT integration · da50d68b
      oai authored
      da50d68b
    • Cedric Roux's avatar
      cleanup MAC PDU generation (plus some general cleanup) · 1a8d81ba
      Cedric Roux authored
      The code was very unclear and potentially buggy.
      This new version is more robust.
      
      We can waste up to 2 bytes because the last header in the MAC PDU
      does not contain a length field and when we request data from RLC
      we suppose a 3-bytes MAC header. This might be optimized at some
      point, but the benefit would be low.
      
      This commit also contains some general cleanup:
      - formatting
      - variables' types: let's use 'int' instead of trying to be clever
        by using small types that may generate bugs if the value is
        too big
      - remove 'tpc_accumulated' which was globally used for all UEs
        and has no purpose other than logging. We may want to rework
        a bit the TPC machinery at some point. As the code is today
        we may repeatedly send TPC over and over without caring about
        the 3GPP limits, in which case no one knows how the UE is
        supposed to behave: does it clamp the current max value or does
        it accumulate over and over and take the clamped value to compute
        its actual power? If we send a reverse TPC (reduce power instead
        of increase) does it do it immediately or does it have to decrease
        n+1 times if we previously ordered it to increase n times?)
      
      We do not address the problem of prioritizing LCIDs. As of today there
      is only one dedicated traffic channel (DTCH), so it's not a problem
      at this point.
      
      What has been tested:
      - monolithic eNB 5/10/20MHz with one cots UE, TCP/UDP UL/DL. At 20MHz the
        machine used was not capable of keeping up, generating lots of Us
        and Ls when the throughput reaches 60Mb/s. USRP B210 was used.
      1a8d81ba
  5. 22 Feb, 2018 3 commits
  6. 20 Feb, 2018 1 commit
  7. 19 Feb, 2018 1 commit
  8. 16 Feb, 2018 1 commit
    • Cedric Roux's avatar
      bugfix: fix bad conflict resolutions from previous commits · 2d6dd02b
      Cedric Roux authored
      Some more fixes for some bad conflict resolutions.
      
      I ran:
      
          git diff 2018.w04 2018.w05
      
      And saw some problems with config_sib2.
      
      There was also something strange in openair2/LAYER2/openair2_proc.c
      in the function dump_eNB_l2_stats. Maybe the fix is wrong for
      this one. To be checked.
      2d6dd02b
  9. 15 Feb, 2018 1 commit
    • Cedric Roux's avatar
      integration fix: set default max MCS for UL back to 20 · c0be5a12
      Cedric Roux authored
      Doing an iperf UDP uplink test, we could reach only 6Mb/s
      with very good radio conditions instead of around 8Mb/s.
      
      It turns out the MCS was limited to 16.
      
      With this commit, we are back to a bit more than 8Mb/s
      as it used to be.
      
      (This is with a 5MHz bandwidth.)
      c0be5a12
  10. 14 Feb, 2018 1 commit
  11. 13 Feb, 2018 4 commits
  12. 12 Feb, 2018 6 commits
  13. 09 Feb, 2018 1 commit
  14. 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
  15. 06 Feb, 2018 1 commit
    • Cedric Roux's avatar
      bugfix: fix UL over scheduling · eccb96c4
      Cedric Roux authored
      There is too much UL scheduling because the buffer status is
      overestimated.
      
      This commit tries to make things simpler.
      eccb96c4
  16. 05 Feb, 2018 1 commit
  17. 03 Feb, 2018 2 commits
  18. 31 Jan, 2018 8 commits
  19. 25 Jan, 2018 1 commit