1. 30 Apr, 2018 2 commits
  2. 17 Apr, 2018 1 commit
  3. 12 Apr, 2018 1 commit
  4. 06 Apr, 2018 3 commits
  5. 05 Apr, 2018 2 commits
  6. 29 Mar, 2018 1 commit
  7. 27 Mar, 2018 1 commit
  8. 23 Mar, 2018 3 commits
  9. 22 Mar, 2018 3 commits
  10. 21 Mar, 2018 1 commit
  11. 20 Mar, 2018 3 commits
  12. 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
  13. 15 Mar, 2018 1 commit
  14. 14 Mar, 2018 1 commit
  15. 09 Mar, 2018 3 commits
  16. 08 Mar, 2018 4 commits
    • oai's avatar
      more NB-IoT integration · da50d68b
      oai authored
      da50d68b
    • oai's avatar
    • oai's avatar
    • 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
  17. 06 Mar, 2018 2 commits
  18. 05 Mar, 2018 1 commit
  19. 02 Mar, 2018 3 commits
    • Robert Schmidt's avatar
      4924b18e
    • Robert Schmidt's avatar
      8cace653
    • Cedric Roux's avatar
      hotfix: fix bad RLC UM packet creation · 26d68e9c
      Cedric Roux authored
      Running TCP DL traffic with one connected UE showed a lot of
      fluctuations in throughput. After analysis it was found that
      sometimes the RLC UM PDU was not correct. It contained one byte
      more than it should. On the receiver side, the TCP packet
      contained in the RLC packet seems to be rejected by the TCP
      stack of the UE (it has one byte more than it should),
      leading to a brutal reduction of the throughput, probably due
      to some congestion detection in the TCP implementation.
      Or something.
      
      This hotfix seems to solve the problem. Using iperf in downlink
      with a 5MHz eNB, we see no more fluctuations, the traffic is
      very steady at 16.8Mb/s, as reported by the iperf server running
      on the phone. (17.5 in the PHY plot of the T tracer.)
      
      A rewrite of both the MAC and RLC UM packet generation is needed.
      The code is way too complex for what it does and may contain
      several similar problems that only trigger in specific rare
      conditions.
      26d68e9c
  20. 01 Mar, 2018 2 commits
  21. 28 Feb, 2018 1 commit