1. 09 Sep, 2021 1 commit
  2. 03 Sep, 2021 6 commits
  3. 02 Sep, 2021 6 commits
  4. 01 Sep, 2021 4 commits
  5. 31 Aug, 2021 3 commits
  6. 30 Aug, 2021 1 commit
    • David Kim's avatar
      Fix to handle multiple UEs and typo bug. · 86d605ee
      David Kim authored
      1. Changed hard coded preamble index(63) to soft coded.
      2. Active UE will not be considered in gNB scheduging RA.
      3. Added condition to process dci indication to handle multiple UEs.
      4. Bug fix in mutex_lock (unlock to lock). It should be lock rather than unlock.
      5. nr_ue_scheduler update not to entering into getting IP traffic to be transmitted in noS1 mode.
      6. log update in checking the number of rx_ind or crc
      86d605ee
  7. 27 Aug, 2021 1 commit
  8. 26 Aug, 2021 2 commits
    • Melissa Elkadi's avatar
      Error checking for processing DL PDUs · 6ec545e2
      Melissa Elkadi authored
      Also, we only should be handling/generating AM
      PDUs in the PDCP/RLC layer, not UM PDUs. Updated
      the pre-configuration settings. This seemed to
      make the uplink traffic work (meaning it gets
      from NR UE to the gNB to the EPC). Woo! Still
      working on the downlink.
      6ec545e2
    • Melissa Elkadi's avatar
      Get IP traffic in MAC layer and handling of RAR · cad11751
      Melissa Elkadi authored
      Previously, we would assume every downlink in
      slot 7 was an RAR; now we assume every slot 7
      that occurs before the CFRA procedure is done
      is an RAR. Also changed the logic in scheduler
      to allow us to get nr_ue_sdus in the MAC layer.
      cad11751
  9. 25 Aug, 2021 6 commits
  10. 24 Aug, 2021 2 commits
  11. 23 Aug, 2021 2 commits
  12. 20 Aug, 2021 4 commits
    • Melissa Elkadi's avatar
      Need to call scheduler after RACH indefinitly · 1116d16d
      Melissa Elkadi authored
      The ue_sched_mode is reset to 0 again when we
      memset the ul_info and after the CFRA procedure
      is complete, then uplink CRCs with the PUCCH
      response (PUSCH) are not being sent because the
      scheduler isnt being called. This makes the
      gNB run out of uplink harq ids since its never
      getting the proper responses. The change below
      will ensure that we call the scheduler AFTER the
      RACH is sent and all the time after that.
      1116d16d
    • Melissa Elkadi's avatar
      Making sure we never are in ONLY_PUSCH mode · 671f461e
      Melissa Elkadi authored
      When running on some machines, the ue_sched_mode
      will be initialized to zero. This will cause
      the ul_info the go into the ONLY_PUSCH mode.
      We do not want to ever call the scheduler and return.
      Furthermore, we only want to call the scheduler after
      the NRUE has sent the RACH_IND to the gNB.
      671f461e
    • Melissa Elkadi's avatar
      Setting ue_sched_mode after filling RACH_IND · 0eb90bd8
      Melissa Elkadi authored
      Also, removed the check before calling the
      nr_uescheduler that was associated with the
      ra.state. Lastly, removed the DL_HARQ_PID
      position change as that was incorrect.
      0eb90bd8
    • Melissa Elkadi's avatar
      DCI format options were being set incorrectly. · e6709fe9
      Melissa Elkadi authored
      Had to add a check for our NSA mode. If we are in
      NSA mode, the DCI format options should be populated
      with formats 1 and 7 exclusively. This fixed the
      DLBWP calculation for the PDCCH PDUs.
      e6709fe9
  13. 19 Aug, 2021 2 commits