An error occurred fetching the project authors.
  1. 08 Jun, 2019 1 commit
  2. 26 Mar, 2019 1 commit
  3. 23 Mar, 2019 1 commit
  4. 08 Mar, 2019 1 commit
  5. 22 Feb, 2019 1 commit
  6. 18 Jan, 2019 1 commit
    • Robert Schmidt's avatar
      F1AP: when UL_sync failure, send UEContextRelReq · 7df82575
      Robert Schmidt authored
      When a phone loses connection, it should not simply be removed but first
      CU should be informed which will send a ContextRelCmd. Correspondingly,
      when the RRC releases the UE, it does not send a UE Context Release Req
      7df82575
  7. 07 Dec, 2018 1 commit
  8. 16 Nov, 2018 1 commit
  9. 07 Nov, 2018 1 commit
  10. 25 Oct, 2018 1 commit
  11. 17 Oct, 2018 1 commit
  12. 23 Sep, 2018 1 commit
  13. 21 Sep, 2018 2 commits
  14. 16 Sep, 2018 1 commit
  15. 15 Sep, 2018 2 commits
  16. 13 Sep, 2018 1 commit
  17. 31 Aug, 2018 1 commit
    • Bing-Kai Hong's avatar
      F1 & MAC: · 3021cf11
      Bing-Kai Hong authored
      1. Fix UE_CONTEXT_SETUP_REQUEST and CONTEXT_MODIFICATION_REQUEST encode/decode
      2. Add gNB_DU_CONFIGURATION_UPDATE and gNB_CU_CONFIGURATION_UPDATE procedure
      3. Add C_RNTI_TO_BIT_STRING function
      4. Add INITIAL_UL_RRC_MESSAGE_TRANSFER procedure and with mac_du_data_ind (MSG3)
      5. Add GNB-CUSystemInformation extension part for the F1SetupResponse procedure
      3021cf11
  18. 27 Aug, 2018 1 commit
  19. 24 Aug, 2018 1 commit
  20. 30 Jul, 2018 2 commits
  21. 13 Jul, 2018 1 commit
    • Bi-Ruei, Chiu's avatar
      Use an un-official community collaboration version of asn1c · a247907d
      Bi-Ruei, Chiu authored
      1. It's no need to modify LTE-RRC's ASN.1 file for enabling option group
         feature in generate_asn1.
      2. It's no need to patch the C header files generated from
         LTE-RRC/S1AP/X2AP's ASN.1 in fix_asn1.
      3. It's no need to pre-process S1AP/X2AP's ASN.1 for enabling information
         object class feature by asn1tostruct.py.
      
      This commit requires an un-official version of asn1c which are
      collaboration of asn1c community members and `build_helper` is modified
      in this commit accordingly :
      
        https://github.com/brchiu/asn1c/tree/velichkov_s1ap_plus_option_group
      
      This asn1c can also convert ASN.1 of 5G NR RRC (38.331, v15.1.0) and
      generate C files with -findirect-choice command line option without
      tweaking ASN.1 file.
      
      Examples for how to use this asn1c for S1AP are in S1AP files, e.g.
      s1ap_eNB_nas_procedures.c and s1ap_eNB_handler.c.
      
      There is an modified openair-cn (based on tag 0.5.0) with this new asn1c at :
      
        https://github.com/brchiu/openair-cn/tree/new-asn1c
      
      Basic S1AP interaction and data transfer operation between OAI eNB and
      this modified openair-cn has been tested.
      
      Note: Community version of asn1c is keeping evolved to provide better usage.
      a247907d
  22. 25 Jun, 2018 1 commit
  23. 22 Apr, 2018 1 commit
  24. 08 Apr, 2018 1 commit
  25. 12 Feb, 2018 1 commit
  26. 01 Feb, 2018 1 commit
  27. 21 Jan, 2018 1 commit
  28. 15 Jan, 2018 2 commits
    • Cedric Roux's avatar
      Fix NFAPI integration · 922b5b59
      Cedric Roux authored
      This commit fixes issues introduced by the previous commit.
      
      Summary of work:
      - cleanup:
        - fix LOG_XX to be less verbose
        - fix cmake_targets/CMakeLists.txt
        - fix oaienv
        - remove dead code
      - bug fixes:
        - in openair1/SCHED/fapi_l1.c we had:
            eNB->pdcch_vars[subframe&1].num_dci           = number_dci;
          should be:
            eNB->pdcch_vars[subframe&1].num_dci           = 0;
          This bug let the PHY send more DCIs than what should have been
          sent because num_dci is incremented later on in the code.
          This fix may be a problem for fapi mode, to be checked.
        - add new T VCD traces
        - revert openair1/PHY/TOOLS/file_output.c to 'develop' version
        - remove thread_id in logRecord/logRecord_mt
        - revert (and adapt) configuration files
        - be careful when doing frame++, we need to % 1024
        - revert target_rx_power in openair2/LAYER2/MAC/eNB_scheduler_ulsch.c
      - NFAPI:
        - the open-nFAPI code has been included in the repository. See nfapi/README.
          Maybe we should "git clone" the Cisco repository instead. We have to be
          careful of availability though.
      
      What has been tested:
      - monolithic eNB FDD 5/10MHz with one UE, iperf UDP/TCP uplink/downlink
      
      Anything else may fail to work, especially the FAPI mode, which has not
      been tested at all.
      922b5b59
    • Cedric Roux's avatar
      import NFAPI work from David Price from Cisco (non-working commit, do not use it) · 7757b9e7
      Cedric Roux authored
      It has been chosen to not include the full history of commits
      from David. He included a binary version of wireshark, probably
      a modified one that understands NFAPI. Wireshark is released under
      the GPL license, we cannot include it in the repository. We could
      have done a next commit to remove this binary. But then it would
      still be present in the history of commits, which may not be allowed.
      And it would take space on disk. We could edit the history to remove
      wireshark entirely. But this operation is too complicated.
      
      There was also a pcap capture file, which has nothing to do in
      the history of commits and would take space on disk. There again,
      it's too difficult to edit the history to remove it.
      
      There was a file .gitignore that was also removed.
      
      The original history can be found on David's repository:
      https://gitlab.eurecom.fr/daveprice/openairinterface5g/
      The branch is: nfapi-ru-rau-split.
      
      A copy of that branch has been included in the internal OAI
      repository, for those who have access to it.
      The branch is the same. The last commit ID is
      9106438239e0bc626ff1fa1d97d911caadd0fbb9.
      
      You can compare the current commit with the commit 9106...
      to see what differs.
      
      The current commit has to be considered non-working.
      The commit following the current commit will fix problems with
      the work in the current commit.
      
      If you use git bisect, don't spend time analyzing the current
      commit.
      7757b9e7
  29. 12 Dec, 2017 1 commit
  30. 28 Nov, 2017 2 commits
  31. 23 Oct, 2017 1 commit
  32. 20 Sep, 2017 1 commit
  33. 19 Sep, 2017 1 commit
  34. 14 Sep, 2017 1 commit
  35. 14 Aug, 2017 1 commit