Skip to content
Snippets Groups Projects
  1. Jan 23, 2018
  2. Jan 22, 2018
  3. Jan 19, 2018
    • Cédric Roux's avatar
      Merge remote-tracking branch 'origin/develop_integration_2018_w03' into develop · 91dd7ed4
      Cédric Roux authored
      Summary of changes:
      - Implementation of paging (see issue #255 in gitlab)
      - Implementation of RRC RE-ESTABLISHMENT (see issue #256 in gitlab)
      - Implementation of RRC CONNECTION RELEASE (see issue #257 in gitlab)
      
      Some modifications with timers have been done.
      Expect (and report) problems, thanks.
      
      What has been tested:
      - monolithic eNB 5 and 10MHz with one commercial UE. UDP and TCP
        traffic, uplink and downlink, with iperf (with a third party
        EPC, not openair-cn). TCP downlink traffic is not stable.
        Reason yet unknown. Will be fixed later.
      2018.w03
      91dd7ed4
    • Cédric Roux's avatar
      integration fix: add T trace · 3a867ac7
      Cédric Roux authored
      3a867ac7
  4. Jan 17, 2018
  5. Jan 16, 2018
  6. Jan 15, 2018
  7. Jan 11, 2018
  8. Jan 09, 2018
  9. Jan 08, 2018
  10. Jan 04, 2018
    • Cédric Roux's avatar
      Add support for Ubuntu 17.04 and 17.10. · ec56a416
      Cédric Roux authored
      Basically, build_helper has been adapted so that:
        ./buil_oai -I -w USRP
      works for Ubuntu 17.04 and 17.10.
      
      Concerning those systems:
      - compilation with "--eNB --UE -w USRP" works
      - the enb softmodem runs on 17.04 (not tested on 17.10)
      - nothing else has been tested.
      
      Users should report any problem.
      ec56a416
  11. Jan 03, 2018
    • Cédric Roux's avatar
      hotfix: clear DCI padding bits · c5ca2bd8
      Cédric Roux authored
      The problem is the following (as reported by an user):
      
        "one UE is attached to OAI system. UE is near the antenna. Try to detach
        the UE and attach again. Repeat this procedure for 5-6 times. OAI system
        does not work and any the UE can not attach to this system. I use TEMS
        software and I can see MIB signaling on this UE but UE can not decode SIB1
        and SIB2."
      
      What happens is that the DCI for SIB1 and SIB2 is not cleared before
      use. That is the bits in the 'padding' field keep the values that were
      set before. If the structure has been used to transmit other DCIs
      (eg. for UEs) in the past, it may be reused with some of those bits set
      to 1. When receiving this DCI, the UE won't accept it because it
      gets some bits at 1 where it expects them to be 0.
      
      The short-term/quick solution is to clear the 'padding' field.
      A better solution would be to rewrite this part of the code,
      which is way too complicated for what it does. But this takes
      too much time.
      
      In dci.h the field 'dummy' of some structures was renamed to 'padding'.
      The fields 'padding32' and 'padding64' were also renamed to 'padding'
      for consistency.
      
      Some structures (DCI2B_1_5MHz_TDD, DCI2B_10MHz_FDD, DCI2D_1_5MHz_FDD,
      DCI2D_5MHz_FDD, DCI2D_10MHz_FDD) had a 'padding' field at the end, which
      was renamed to 'padding0'. I don't know if this field should be here at all.
      To me this field looks very suspicious. When we test DCIs 2B and 2D we
      should be careful.
      c5ca2bd8
Loading