An error occurred fetching the project authors.
  1. 10 Jun, 2024 1 commit
  2. 03 Jun, 2024 2 commits
  3. 23 May, 2024 1 commit
  4. 15 May, 2024 1 commit
  5. 17 Apr, 2024 1 commit
  6. 11 Apr, 2024 1 commit
    • Jaroslava Fiedlerova's avatar
      Add ulsch decoding statistics measurements · efe06546
      Jaroslava Fiedlerova authored
      Add ulsch decoding measurements, which are reported by nr_ulsim. Start ulsch_decoding_stats measurement before
      nr_ulsch_decoding is called and stop it after collection of all decoder tasks from Tpool. In the context of nr_ulsim,
      ULSCH_id is allways == 0, testing is performed per one TB, therefore measurement is started and stopped only once per trial.
      Reported ulsch decoding statistics show the mean ulsch decoding time over x trials (specified by -n command line option of nr_ulsim).
      This measurement does not provide valid information in case of nr-softmodem, when the loop is done over multiple ULSCH IDs -
      start of the measurement is done multiple times and stops only once in this case.
      For unitary physical simulators, ULSCH processing loop is executed only once
      - the max number of PUSCH is set to 1. This ensures exactly one start and stop
      of the ULSCH decoding time measurement per processed TB.
      
      Note: ulsch decoding statistics reports average time of segmentation, rate matching, interleaving and decoding of the TB
      efe06546
  7. 09 Apr, 2024 1 commit
  8. 26 Mar, 2024 1 commit
  9. 07 Mar, 2024 1 commit
  10. 04 Mar, 2024 1 commit
  11. 12 Feb, 2024 2 commits
    • Robert Schmidt's avatar
      Remove misleading PUSCH decoding · 362bc481
      Robert Schmidt authored
      PUSCH decoding is started multiple times in nr_ulsch_procedures() for
      each ULSCH segment, and stopped once inside
      phy_procedures_gNB_uespec_RX(). Not only is it not clear if that works
      with the API, it also might measure more than just PUSCH decoding.
      
      Remove the PUSCH decoding, it is misleading. Check L1 RX processing
      instead.
      362bc481
    • Raymond Knopp's avatar
      Introduce separate thread to handle gNB TX processing · d52b8179
      Raymond Knopp authored
      This commit introduces a separate thread (l1_tx_thread) that processes
      gNB DL/TX slots. It receives a message from the ru_thread when a new
      slot started, and starts processing.
      
      The DL part of the scheduler is run in the l1_tx_thread.  Therefore,
      only call UL indication (for scheduler) in UL slots.  The UL indication
      previously triggered the DL scheduler -- hence, it had to be called in
      every slot. Now, since the DL scheduler is moved into the DL thread, we
      don't have to call the scheduler in every slot anymore.
      
      The reorder thread is removed, as reordering with this scheme is not
      necessary anymore.
      
      The main advantage of this version is that the TX can be scheduled
      earlier (sl_ahead). Further, there can no longer be race conditions in
      the TX path, since the scheduler/L2, TX L1 processing and the RU tx
      function are all execute in the same thread (L1_tX_thread).
      
      Also, the scheduler prepares PRACH/PUSCH/PUCCH FAPI PDUs. As of this
      commit, the scheduler runs in the TX processing chain, whereas these
      PDUs are destined for RX processing.  Thus, too avoid data races,
      instead of triggering the RX processing at the same time as TX
      processing in the RU thread, this commit changes the code to trigger RX
      processing after the scheduler has been run in TX processing to avoid
      data races.
      
      Finally, we synchronize RU and L1 threads. This is important for
      rfsimulator, since unlike most radios, rfsimulator can run slower or
      faster, depending on I/O and CPU (it does not have a stable "tick").
      Co-authored-by: default avatarkiran <saikiran@iitj.ac.in>
      d52b8179
  12. 24 Jan, 2024 1 commit
  13. 23 Jan, 2024 1 commit
  14. 19 Jan, 2024 1 commit
  15. 20 Dec, 2023 1 commit
  16. 01 Dec, 2023 1 commit
  17. 28 Nov, 2023 3 commits
  18. 20 Nov, 2023 3 commits
  19. 10 Nov, 2023 2 commits
  20. 03 Nov, 2023 1 commit
  21. 27 Oct, 2023 3 commits
  22. 10 Oct, 2023 1 commit
    • francescomani's avatar
      Use SRB0 at UE · 91891299
      francescomani authored
      - Use SRB0 TM entity at UE for Msg.3/RRC Setup Request
      - Msg3 data request sent upon reception of Msg2, then we get data from
        rlc when needed
      91891299
  23. 06 Oct, 2023 1 commit
  24. 25 Sep, 2023 3 commits
  25. 22 Sep, 2023 5 commits