An error occurred fetching the project authors.
  1. 19 Mar, 2021 8 commits
  2. 11 Mar, 2021 1 commit
  3. 10 Mar, 2021 1 commit
  4. 03 Mar, 2021 1 commit
    • 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
  5. 01 Mar, 2021 1 commit
  6. 26 Feb, 2021 13 commits
  7. 19 Feb, 2021 1 commit
  8. 12 Feb, 2021 2 commits
  9. 11 Feb, 2021 1 commit
  10. 09 Feb, 2021 1 commit
  11. 07 Feb, 2021 10 commits