1. 26 Apr, 2019 2 commits
  2. 19 Apr, 2019 2 commits
  3. 05 Apr, 2019 1 commit
  4. 03 Apr, 2019 1 commit
    • Cedric Roux's avatar
      bugfixes for the ue T tracer · 4905a5e8
      Cedric Roux authored
      Not much major changes. In openair1/PHY/LTE_UE_TRANSPORT/dci_tools_ue.c,
      in the function generate_ue_dlsch_params_from_dci,
      'harq_pid' was removed and dci_info_extarcted.harq_pid is now used for
      all cases.
      
      The ue T tracer only deals with PHY signals (no MAC, RLC, PDCP, RRC).
      4905a5e8
  5. 26 Mar, 2019 1 commit
  6. 19 Mar, 2019 4 commits
    • Cedric Roux's avatar
      PHY: add parameter end_of_burst_delay for TDD · 275e5b3a
      Cedric Roux authored
      end_of_burst_delay is used to stop TX only "after a while".
      If we stop right after effective signal, with USRP B210 and
      B200mini, we observe a high EVM on the S subframe (on the
      PSS).
      A value of 400 (for 30.72MHz) solves this issue. This is
      the default.
      
      This default value can be changed in the configuration file.
      For example:
      
      RUs = (
          {
             local_rf       = "yes"
               nb_tx          = 1
               nb_rx          = 1
               att_tx         = 20
               att_rx         = 0;
               bands          = [7];
               max_pdschReferenceSignalPower = -27;
               max_rxgain                    = 105;
               eNB_instances  = [0];
               sf_extension = 312;
               end_of_burst_delay = 200;
          }
      );
      
      Here we would set a value of 200.
      
      The value to put in the configuration file is for
      30.72MHz. The value is scaled accordingly at runtime
      (thus only one value to set for every RB configuration,
      25, 50 or 100, leading to less problems when adapting
      configuration files).
      
      This option is for experts and should not be changed
      randomly.
      275e5b3a
    • Cedric Roux's avatar
      PHY: bugfix: compute start/end of burst correctly for TDD · a05753df
      Cedric Roux authored
      Start of burst is to start TDD DL transmission in the driver
      (tested with USRP for the moment).
      
      End of burst is to stop DL transmission.
      
      Start of burst can only happen for a DL subframe when the
      previous subframe was an UL subframe.
      
      End of burst can only happen for an S subframe.
      
      It's impossible for a subframe to be both the start of a burst
      and the end of a burst.
      
      This can be checked with eg. http://niviuk.free.fr/lte_resource_grid.html
      (or reading the specs).
      a05753df
    • Cedric Roux's avatar
    • Cedric Roux's avatar
      PHY: make sf_extension a parameter · ee5b7390
      Cedric Roux authored
      This parameter is meaningful in TDD, to decide
      when to start DL at eNB side. Since there is a
      need for the PA to be operational, we need to
      transmit a bit before the DL subframe coming
      after an UL subframe. (We transmit zeros.)
      
      We used to use N_TA_offset which may be too much.
      Default value is now N_TA_offset/2 and can be
      changed in the configuration file, in the RUs
      section, like:
      
      RUs = (
          {
             local_rf       = "yes"
               nb_tx          = 1
               nb_rx          = 1
               att_tx         = 0
               att_rx         = 0;
               bands          = [7];
               max_pdschReferenceSignalPower = -27;
               max_rxgain                    = 105;
               eNB_instances  = [0];
               sf_extension = 312;
          }
      );
      
      N_TA_offset is 624 (for 30.72MHz). In the example
      above, we set sf_extension = 312, which is also
      the default.
      
      The value to put in the configuration file is for
      30.72MHz. The value is scaled accordingly at runtime
      (thus only one value to set for every RB configuration,
      25, 50 or 100, leading to less problems when adapting
      configuration files).
      
      This option is for experts and should not be changed
      randomly.
      ee5b7390
  7. 16 Mar, 2019 1 commit
  8. 14 Mar, 2019 1 commit
  9. 13 Mar, 2019 1 commit
    • Cedric Roux's avatar
      x2ap: timers, cleanup · 9456fe58
      Cedric Roux authored
      This commit introduces X2AP timers (t_reloc_prep, tx2_reloc_overall).
      You need to set the values in the configuration file.
      
      X2AP can be enabled or disabled in the configuration file too (disabled
      by default).
      
      Some deadcode was removed.
      9456fe58
  10. 09 Mar, 2019 1 commit
  11. 08 Mar, 2019 1 commit
  12. 05 Mar, 2019 2 commits
  13. 04 Mar, 2019 1 commit
  14. 27 Feb, 2019 2 commits
    • Robert Schmidt's avatar
      1e3d0c9a
    • Cedric Roux's avatar
      bugfix: fix PDCP sequence management (plus some cleanup) · e3782b5c
      Cedric Roux authored
      With the introduction of X2AP into develop, the UEs now have to regularly
      send measurement reports.
      
      In the logs of the eNB, we see:
      
      [OSA]   Mismatch found in integrity for algorithm 2,
              got e0.a0.c2.66, expecting a5.9c.cb.57
      [PDCP]   [OSA][RB 1] eNB failed to validate MAC-I of incoming PDU
      
      This is a bug in the PDCP layer that uses wrong parameters to compute the
      integrity.
      
      This commit fixes this bug.
      
      The function pdcp_is_rx_seq_number_valid was removed. Its processing
      has been directly integrated into the function pdcp_data_ind.
      
      The function pdcp_mark_current_pdu_as_received is not called anymore.
      Its processing was not used later on, so as of today, not calling it does
      not introduce any functional change.
      
      The function pdcp_validate_security takes now as parameters both
      SN and HFN. Same for the function pdcp_get_next_count_rx.
      
      Useless constants PDCP_SN_5BIT, PDCP_SN_7BIT and PDCP_SN_12BIT have been
      removed.
      
      The compilation option ENABLE_SECURITY has been removed. It's now always
      on. (This may impact some use cases.)
      
      The PDCP for DRB using RLC AM is not correct. It was not correct before
      this commit (apart from the integrity bug). We should deal with a list
      of PDUs and transmit packets to upper layers as detailed in the specs.
      Today we transmit the PDU as soon as we get it. We don't care about
      duplicates, in-order delivery, timeouts.
      
      Also, we don't deal with "PDCP re-establishment". Not sure how that impacts
      the software.
      
      And, last but not least, there is still no ROHC.
      e3782b5c
  15. 25 Feb, 2019 2 commits
  16. 22 Feb, 2019 1 commit
  17. 21 Feb, 2019 1 commit
  18. 20 Feb, 2019 1 commit
  19. 19 Feb, 2019 1 commit
  20. 17 Feb, 2019 2 commits
  21. 13 Feb, 2019 2 commits
  22. 12 Feb, 2019 5 commits
  23. 29 Jan, 2019 1 commit
  24. 24 Jan, 2019 3 commits