An error occurred fetching the project authors.
  1. 13 Mar, 2024 1 commit
  2. 12 Mar, 2024 1 commit
  3. 06 Mar, 2024 1 commit
  4. 15 Feb, 2024 1 commit
  5. 08 Feb, 2024 2 commits
  6. 04 Feb, 2024 1 commit
  7. 02 Feb, 2024 2 commits
  8. 30 Jan, 2024 1 commit
  9. 25 Jan, 2024 2 commits
  10. 22 Jan, 2024 1 commit
  11. 19 Jan, 2024 3 commits
  12. 15 Jan, 2024 1 commit
  13. 08 Jan, 2024 1 commit
  14. 04 Jan, 2024 1 commit
  15. 20 Dec, 2023 4 commits
  16. 19 Dec, 2023 2 commits
  17. 20 Nov, 2023 3 commits
  18. 16 Nov, 2023 1 commit
  19. 27 Oct, 2023 1 commit
  20. 16 Oct, 2023 1 commit
  21. 10 Oct, 2023 3 commits
  22. 22 Sep, 2023 3 commits
  23. 12 Aug, 2023 1 commit
    • Robert Schmidt's avatar
      Repair reestablishment and make it work via F1 · 7a298e73
      Robert Schmidt authored
      This commit repairs the reestablishment after the introduction of the CU
      UE ID in the CU, different from the DU UE ID. Now, the CU uses an
      identifier different from the RNTI, used in the MAC, to refer to UEs.
      
      To repair the reestablishment, a number of changes needed to be
      introduced:
      
      - Handle old_gNB_DU_UE_id in MAC
      
      The MAC handles the old_gNB_DU_UE_id field in the DL RRC Message. The
      commit adds encoding/decoding of the field. The MAC will drop the old
      UE, but retain the CellGroup of the corresponding UE(!). Because a UE
      releases the spCellGroup on reestablishment, the MAC does the same; it
      needs to reapply the old configuration after a reconfiguration. For the
      latter, introduce new variables to keep a "future" CellGroupConfig to be
      applied (reconfigCellGroup) and a flag (expect_reconfiguration) that
      applies the CellGroupConfig if a DL RRC Message transfer on DCCH, which
      is assumed to be the reconfiguration.
      
      - Add RNTI change in RLC
      
      The RLC needs to reuse the old UE context. Hence, we simply change the
      RNTI in the old context, and delete the new one.
      
      - No PDCP UE ID change
      
      The previous implementation of the PDCP used the RNTI; hence, the ID
      needed to be switch (as above for the RLC). Since the PDCP now also uses
      the CU UE ID, no identifier change is needed, and we remove all
      corresponding code.
      
      - No MAC modifications/update from CU
      
      As foreseen by the spec, the CU does not modify or change the
      cellGroupConfig in the RRC during reestablishment. This change will be
      generalized in the future to all of the RRC.  Also, the
      nr_rrc_mac_remove_ue() function has been removed: the MAC handles any UE
      changes autonomeously, without being triggered from the RRC explicitly.
      
      - Remove reestablish_rnti_map
      
      The RRC does not use RNTIs for UE identification. Hence, a
      reestablish_rnti_map to link two UEs to each other is not necessary
      anymore.
      7a298e73
  24. 28 Jul, 2023 1 commit
    • Thomas Schlichter's avatar
      fix limited UL data throughput in do-ra mode · f1a09505
      Thomas Schlichter authored
      In case of noS1-mode, we initialize the 'logicalChannelBearer_exist' array element for the pre-configured DRB0 in function 'nr_l2_init_ue()'.
      That array is indexed with the LCID.
      For DRB0, the LCID is 4.
      Unfortunately, the code incorrectly used the array at index 0.
      Therefore, the UE sent neither scheduling requests nor buffer status reports, what resulted in extremely poor UL throughput.
      f1a09505
  25. 05 May, 2023 1 commit