1. 23 Jan, 2025 11 commits
  2. 22 Jan, 2025 2 commits
  3. 21 Jan, 2025 1 commit
  4. 20 Jan, 2025 3 commits
  5. 17 Jan, 2025 5 commits
  6. 16 Jan, 2025 1 commit
    • Robert Schmidt's avatar
      Merge branch 'integration_2025_w03' into 'develop' · 10e07bc6
      Robert Schmidt authored
      Integration: `2025.w03`
      
      See merge request oai/openairinterface5g!3206
      
      * !3167 remove calls to clear SIMD registers, that was a historical issue
      * !3179 UE statistics improvements
      * !3193 Remove spinlock from threadpool task return
      * !3195 UE MAC: in phy-test/do-ra, fill TB randomly
      * !3201 T tracer: minor fixes for compilation
      * !3204 CI: Increase number of test trials for timing tests
      * !3034 Delay compensation for PUCCH2
      * !3205 Fix calculation of RSSI in pucch_rx.c
      10e07bc6
  7. 15 Jan, 2025 12 commits
  8. 14 Jan, 2025 5 commits
    • Bartosz Podrygajlo's avatar
      Remove spinlock from threadpool task return · 0657ab22
      Bartosz Podrygajlo authored
      The idea to use atomic aligned to cache line for counting finished jobs
      is reused, but instead of polling a semaphore was added
      0657ab22
    • Guido Casati's avatar
      9e9bd278
    • Guido Casati's avatar
      Refactor SCTP association response handler · bcd12702
      Guido Casati authored
      * this function is used by both CU-CP and CU-UP
      * it behaves differently depending on the type of E1 instance:
        CU-CP: inform RRC of E1 connection loss with CU-UP
        CU-UP: trigger a new SCTP association request by sending an ITTI to the CU-UP task
      * after receiving the E1AP register request, the CU-UP will send a new association request to
        SCTP until new E1 connection is achieved by sending a TIMER_HAS_EXPIRED message to the CU-UP
        task. The function e1apHandleTimer() is basically triggering a new E1 association request
        until new E1 connection is achieved
      * print SCTP association state in e1ap.c whenever needed
      
      Related to #878
      bcd12702
    • Guido Casati's avatar
      Clean up NGAP Setup Failure messages: there's no such message in 3GPP TS 38.413 · b922fd26
      Guido Casati authored
      * the list of PDU Session Resources Failed to Setup shall be sent in the Response message
      b922fd26
    • Guido Casati's avatar
      Handle PDU Session Resource to Setup Failure in (PDU Session Resource/Initial... · a1abf90d
      Guido Casati authored
      Handle PDU Session Resource to Setup Failure in (PDU Session Resource/Initial Context) Setup Response
      
      * add function to check whether cu-up is connected
      * add functions to send the relevant response messages with the failed list
        e.g. to fill PDU Session Resource Failed to Setup items
      * set return value of trigger_bearer_setup to bool and handle the
        failure by sending setup response messages with list of PDU sessions failed to setup
        i.e. send failed list of items when no CU-UP is associated to the CU-CP
        note: it considers all PDU Sessions as failed to setup in the considered failure scenarios
      * e.g. send a list of failed PDU session resources in the response message to reject
        PDU Session Resource Setup in rrc_gNB_process_NGAP_PDUSESSION_SETUP_REQ
      * the Initial Context Setup has a Failure message, but for the considered failure scenario
        when no CU-UP is available the current design is just sending a list of failed to setup
        items in the Response message
      * transfer PDU Session Resource/Initial Context Setup Request NAS PDU to UE
      
      closes #878
      a1abf90d