An error occurred fetching the project authors.
  1. 23 Dec, 2020 1 commit
  2. 02 Dec, 2020 1 commit
  3. 13 Oct, 2020 2 commits
    • Robert Schmidt's avatar
      Remove MAX_NUMBER_NETIF and use num UE · a6126a39
      Robert Schmidt authored
      a6126a39
    • Robert Schmidt's avatar
      Remove UESIM_EXPANSION · 4c7035e6
      Robert Schmidt authored
      This completely removes the UESIM_EXPANSION define: it does not compile
      at the moment. Its function was to multiplex multiple UEs on the same
      TUN interface. However, this functionality is not needed since it is
      possible to allocate many TUN devices (i.e., >= 32).
      4c7035e6
  4. 06 Aug, 2020 1 commit
  5. 18 Jun, 2020 2 commits
  6. 12 Jun, 2020 1 commit
  7. 25 May, 2020 1 commit
  8. 13 May, 2020 1 commit
  9. 10 Mar, 2020 1 commit
  10. 22 Jan, 2020 1 commit
  11. 05 Dec, 2019 1 commit
  12. 26 Sep, 2019 1 commit
  13. 24 Sep, 2019 1 commit
  14. 18 Sep, 2019 1 commit
  15. 17 Sep, 2019 1 commit
  16. 16 Sep, 2019 1 commit
  17. 14 Sep, 2019 1 commit
    • Javier Morgade's avatar
      *L2 procedures to enable mixed unicast/broadcast operation at ENB implemeted: · dc14cdc6
      Javier Morgade authored
      	-MBMS scheduler developed (oneFrame allocations implemented at this time)
      	-UE DSLCH schedulers updated: if an eMBMS session running UE DTCH, DCCH will be only scheduled at non MBSFN sufbframes
      	-eMBMS L2 procedures implemented
      	-Dedicated MBMS PDCP pipes src/sink enabled (only for TUN)
      	-BUGFIX eMBMS MAC procedures (wrong indexing at few loops)
      	-ENB FAPI updated to enable dynamic MBSFN configurations through M2AP (RRC<->MCE)
      
      	ACKNOWLEDGEMENT:
       	1. This commit was developed at Vicomtech (https://www.vicomtech.org) under UE project CDN-X-ALL: "CDN edge-cloud computing for efficient cache and reliable streaming aCROSS Aggregated unicast-multicast LinkS"
       	2. Project funded by Fed4FIRE+ OC5 (https://www.fed4fire.eu)
      Signed-off-by: default avatarJavier Morgade <javier.morgade@ieee.org>
      dc14cdc6
  18. 06 Sep, 2019 1 commit
  19. 10 May, 2019 1 commit
  20. 19 Apr, 2019 2 commits
  21. 11 Apr, 2019 1 commit
  22. 08 Apr, 2019 1 commit
  23. 05 Apr, 2019 1 commit
  24. 26 Mar, 2019 1 commit
  25. 09 Mar, 2019 1 commit
  26. 08 Mar, 2019 2 commits
  27. 05 Mar, 2019 1 commit
  28. 27 Feb, 2019 1 commit
    • Cedric Roux's avatar
      bugfix: fix PDCP sequence management (plus some cleanup) · e3782b5c
      Cedric Roux authored
      With the introduction of X2AP into develop, the UEs now have to regularly
      send measurement reports.
      
      In the logs of the eNB, we see:
      
      [OSA]   Mismatch found in integrity for algorithm 2,
              got e0.a0.c2.66, expecting a5.9c.cb.57
      [PDCP]   [OSA][RB 1] eNB failed to validate MAC-I of incoming PDU
      
      This is a bug in the PDCP layer that uses wrong parameters to compute the
      integrity.
      
      This commit fixes this bug.
      
      The function pdcp_is_rx_seq_number_valid was removed. Its processing
      has been directly integrated into the function pdcp_data_ind.
      
      The function pdcp_mark_current_pdu_as_received is not called anymore.
      Its processing was not used later on, so as of today, not calling it does
      not introduce any functional change.
      
      The function pdcp_validate_security takes now as parameters both
      SN and HFN. Same for the function pdcp_get_next_count_rx.
      
      Useless constants PDCP_SN_5BIT, PDCP_SN_7BIT and PDCP_SN_12BIT have been
      removed.
      
      The compilation option ENABLE_SECURITY has been removed. It's now always
      on. (This may impact some use cases.)
      
      The PDCP for DRB using RLC AM is not correct. It was not correct before
      this commit (apart from the integrity bug). We should deal with a list
      of PDUs and transmit packets to upper layers as detailed in the specs.
      Today we transmit the PDU as soon as we get it. We don't care about
      duplicates, in-order delivery, timeouts.
      
      Also, we don't deal with "PDCP re-establishment". Not sure how that impacts
      the software.
      
      And, last but not least, there is still no ROHC.
      e3782b5c
  29. 26 Feb, 2019 1 commit
  30. 25 Feb, 2019 2 commits
  31. 19 Feb, 2019 1 commit
  32. 17 Feb, 2019 1 commit
  33. 12 Feb, 2019 1 commit
  34. 22 Jan, 2019 2 commits