1. 15 Mar, 2021 4 commits
    • Florian Kaltenberger's avatar
    • Robert Schmidt's avatar
    • Robert Schmidt's avatar
      Make RRC buffer sufficiently large · 8307d799
      Robert Schmidt authored
      8307d799
    • Remi Hardy's avatar
      Integration 2021 wk10 · fe49a225
      Remi Hardy authored
      MR !1054 : gNB_multi-threading_rework
      -Replacing the existing multi-threading pipeline with threadPool library, simpler and more robust
      -Updated dlsim to print stats to matlab file.
      -Small fix for UE Ulsch coding.
      
      
      MR !1063 : T_tracer__add_gnb_tracer
      Minimalist gnb tracer to trace (for the moment) rxdataF when some decoding for PUCCH or PUSCH has been done
      
      MR !1070 : nr_pdcp_improvements
      Implement data transfer (38.331 5.2): - transmit operation (in nr_pdcp_entity_recv_sdu) - receive operation (in nr_pdcp_entity_recv_pdu) - t-Reordering expiration
      
      MR !1076 : PBCHNRTCFIX
      Issue Details: If bchPayload is changed to non-zero value, then the test case used to fail.
      Solution: While final check against UE decoded bchpayload and input bchpayload, the AND operation with 0xff is missing along with RIGHT SHIFT operation for input bchpayload.
      
      
      MR !973 : s1_subnormal
      LTE update in S1 functions from Fujitsu.
      -NNSF
      -S1AP auto recovery.
      -Handling unexpected messages.
      -Fix memory leak.
      
      
      MR !1048 : develop_SA_RA
      -Draft and initial trigger of RA procedures upon SIB1 reception. 
      -Improvements on SA SIB1 reception.
      -Get Msg3 from RRC to MAC layer (this fixes random Msg3). 
      -Fix Tables 7.4.1.1.2-1/2 from 38.211.
      
      
      fe49a225
  2. 12 Mar, 2021 4 commits
  3. 11 Mar, 2021 1 commit
  4. 10 Mar, 2021 3 commits
  5. 09 Mar, 2021 6 commits
  6. 08 Mar, 2021 3 commits
  7. 07 Mar, 2021 1 commit
  8. 06 Mar, 2021 1 commit
  9. 05 Mar, 2021 4 commits
  10. 04 Mar, 2021 4 commits
  11. 03 Mar, 2021 6 commits
    • Thomas Schlichter's avatar
    • Thomas Schlichter's avatar
    • cig's avatar
      222933a5
    • cig's avatar
      Minor cleanup UE · f2bc1012
      cig authored
      - removed commented out code
      - improved logging in UL channel estimation
      - minor fixes according to OAI coding guidelines
      - moving fetching TDD configuration parameters in nr-ue.c only in TDD case
      f2bc1012
    • Thomas Schlichter's avatar
      NR_UE: handle initial TA the same way as TA updates, independent of the UE_mode · 01645168
      Thomas Schlichter authored
      In FDD mode, the UE_mode switches to PUSCH mode before the initial TA value was applied.
      Because of this, the ta_command was misinterpreted.
      Fix this by adding 31 to the initial TA comamnd and handle it the same as TA updates.
      01645168
    • Cedric Roux's avatar
      nr pdcp: improvements · 9edc8cce
      Cedric Roux authored
      Implement data transfer (38.331 5.2):
          - transmit operation (in nr_pdcp_entity_recv_sdu)
          - receive operation (in nr_pdcp_entity_recv_pdu)
          - t-Reordering expiration
      
      To keep track of time the function nr_pdcp_wakeup_timer_thread has been
      added and is called by the gNB's MAC scheduler via nr_pdcp_tick.
      
      (The UE has not been modified.)
      
      A thread has been introduced to set time of all the existing PDCP
      entities in the system. This probably does not scale well with many
      PDCP entities (many UEs connected to the gNB). To be changed at some
      point when needed. Hopefully, with a few UEs this mechanism won't be
      too problematic (ie. won't cause realtime problems).
      
      The problem with time in PDCP is that SDUs are kept if some are
      missing, to do reordering. A timer is started and when it expires
      we have to transmit the SDUs even if some are still missing. We
      want to do that as soon as possible. So we have to check timers
      often (every millisecond).
      
      In RLC the time is set when there is some activity (SDU or PDU
      received). In PDCP we cannot wait for this kind of activity. We
      would keep packets longer than necessary, which may disturb
      upper layers (think: TCP). That is why we introduced the thread,
      as a simple mechanism to keep packets no longer than necessary.
      
      The locking done by this thread may create realtime issues.
      
      The whole logic of time keeping can be changed later if it turns
      out that it is not efficient.
      
      The functions dealing with DRB AM have been removed. All the types
      of PDCP entities (DRB AM, DRB UM, SRB) use the same mechanism for
      transmit and receive operations. So the code has been made common
      for all those types.
      
      We don't deal with:
          - entity re-establishment, entity release or entity suspend
          - SDU discard (the timer is present but not used)
          - status reporting
          - data recovery
          - data volume calculation
          - header compression / decompression
      
      There is no plan to implement those features in a near future.
      
      Integrity protection is not done yet, and will be implemented soon.
      9edc8cce
  12. 02 Mar, 2021 3 commits
    • Florian Kaltenberger's avatar
      Update TESTING_GNB_W_COTS_UE.md · fdc818bc
      Florian Kaltenberger authored
      fdc818bc
    • rmagueta's avatar
      Merge remote-tracking branch 'origin/develop' into develop-SA-RA · 5f66269a
      rmagueta authored
      # Conflicts:
      #	openair2/LAYER2/NR_MAC_gNB/gNB_scheduler_ulsch.c
      5f66269a
    • Cedric Roux's avatar
      T tracer: add gnb tracer · 95b659ab
      Cedric Roux authored
      Minimalist gnb tracer to trace (for the moment) rxdataF when some
      decoding for PUCCH or PUSCH has been done.
      
      Important: T_BUFFER_MAX and T_CACHE_SIZE have been changed. T_BUFFER_MAX
      is twice as big as before. T_CACHE_SIZE has been devided by two. Globally,
      the memory usage of the T tracer is the same, but since we divided by two
      the number of buffers in the cache, we may hit some realtime problems if
      all the buffers are busy at some point. The simple solution would be to
      use 8192*2 for T_CACHE_SIZE as it was, but then we double the memory usage
      of the T tracer. This, or another solution, to be defined.
      95b659ab