1. 13 Nov, 2023 2 commits
  2. 12 Nov, 2023 2 commits
  3. 10 Nov, 2023 9 commits
  4. 09 Nov, 2023 1 commit
  5. 08 Nov, 2023 1 commit
    • Robert Schmidt's avatar
      Hack: Prevent CU-UP UE ID management if integrated CU · c36eb7c9
      Robert Schmidt authored
      This is a workaround for a problem described in #706. In short, we
      cannot reuse the cu_add/remove_f1_ue_data() functions if we are in an
      integrated CU-UP/CP ("CU"), but then we can also not reliably use
      different UE IDs in CU-UP and CU-CP (except if using even more hacks).
      c36eb7c9
  6. 06 Nov, 2023 3 commits
  7. 04 Nov, 2023 3 commits
    • Robert Schmidt's avatar
      Only print UE caps if DU available · 31ed25ac
      Robert Schmidt authored
      The DU UE capability printing depends on data on SCS and band, which
      currently is only stored with the DU. To avoid any assert, we check
      that the DU is present. A follow-up commit will rework this.
      31ed25ac
    • Robert Schmidt's avatar
    • Robert Schmidt's avatar
      Free F1 UE data struct only on UE release · 23025837
      Robert Schmidt authored
      Before this commit, as visible in the handler of an F1 UE release, it
      can happen that we forward the RRC Release message to a UE and start the
      release timer, while also removing the F1 UE data (containing e.g., the
      CU UE ID). This can lead to asserts, since there might still be
      subsequent traffic for such UE during a short time, while the DU does
      not have the secondary UE ID stored anymore.
      
      This commit changes the logic. It introduces function
      nr_mac_release_ue() that removes the UE at MAC and RLC, frees the F1 UE
      data (if applicable), and sends the complete, after timing expiry. If
      the UE is out of sync, this function is used to free the UE immediately.
      
      This fixes #685 and #698.
      23025837
  8. 03 Nov, 2023 3 commits
  9. 02 Nov, 2023 3 commits
  10. 31 Oct, 2023 7 commits
  11. 30 Oct, 2023 6 commits