Skip to content

O
OpenXG-RAN
Switch branch/tag
  1. 29 Apr, 2020 1 commit
  3. 11 Feb, 2020 3 commits
  5. 10 Feb, 2020 1 commit
  7. 05 Feb, 2020 1 commit
  9. 04 Feb, 2020 1 commit
  11. 30 Jan, 2020 1 commit
  13. 17 Jan, 2020 1 commit
  15. 15 Jan, 2020 1 commit
  17. 14 Jan, 2020 5 commits
  19. 08 Jan, 2020 1 commit
  21. 23 Dec, 2019 1 commit
  23. 17 Dec, 2019 2 commits
  25. 14 Dec, 2019 4 commits
  27. 04 Dec, 2019 1 commit
  29. 29 Nov, 2019 1 commit
  31. 27 Nov, 2019 1 commit
  33. 19 Nov, 2019 1 commit
  35. 13 Nov, 2019 2 commits
  37. 08 Nov, 2019 5 commits
  39. 07 Nov, 2019 5 commits
    • Raphael Defosseux's avatar
      CI: tuning on TDD scenarios · 7f19d114
      Raphael Defosseux authored 
      Signed-off-by: default avatarRaphael Defosseux <raphael.defosseux@eurecom.fr>
      7f19d114
    • Raphael Defosseux's avatar
      CI: preparing release notes for patch · 0caec0ac
      Raphael Defosseux authored 
       --> also adding TDD monolithic test at 20MHz with default scheduler
 --> putting IF4.p5 TDD scenarios with default scheduler
Signed-off-by: default avatarRaphael Defosseux <raphael.defosseux@eurecom.fr>
      0caec0ac
    • masayuki.harada's avatar
      Fix scheduling PUSCH when CQI has not been received for a long time in fairRR scheduler. · d2346bdf
      masayuki.harada authored
      d2346bdf
    • masayuki.harada's avatar
      Fix cqi_req clear timing, and schedule PUSCH when CQI has not been received... · 85c160dd
      masayuki.harada authored 
      Fix cqi_req clear timing, and schedule PUSCH when CQI has not been received for a long time in fairRR scheduler.
      85c160dd
    • Cedric Roux's avatar
      hotfix: better CQI requests, especially for TDD · e2305bff
      Cedric Roux authored 
      In TDD mode, CQI requests are not possible in special subframes (at
least for some TDD configurations, see 36.213 7.2.3 that says "a
DL subframe is valid if it does not contain a DwPTS field if the
length is less than  7680 Ts").

In the code, we simply disable CQI requests in special subframes,
no matter what the length of DwPTS.

A problem can arise if the DCI0 for a given UE are sent only in
those special subframes. In this case the UE will never report
CQI and the eNB will use low MCS for this UE, impacting performances.

Another, related, problem is when there are several UEs. There again
one UE might always get its DCI0 in special subframes and thus never
report CQI. There again, performance issues.

This commit is an attempt to improve the situation.

It does two things.

1 - tag the UE as schedulable in the function UE_is_to_be_scheduled
    if the cqi_req_timer is expired

2 - use cqi_req_timer as a criterium when ordering UEs for UL scheduling

The value chosen for the expiration of the cqi_req_timer in
UE_is_to_be_scheduled is quite high (300) because as the code is
today we may overschedule the UE for short bursts until we receive
a CQI from the UE. [TODO: fix the code properly to avoid this behavior.]

Note: the fairRR scheduler has not been analyzed and this commit may
      not fix anything in case the fairRR scheduler is used.
      e2305bff
  41. 06 Nov, 2019 1 commit
    • Cedric Roux's avatar
      hotfix: better CQI requests, especially for TDD · 2a7ac81b
      Cedric Roux authored 
      In TDD mode, CQI requests are not possible in special subframes (at
least for some TDD configurations, see 36.213 7.2.3 that says "a
DL subframe is valid if it does not contain a DwPTS field if the
length is less than  7680 Ts").

In the code, we simply disable CQI requests in special subframes,
no matter what the length of DwPTS.

A problem can arise if the DCI0 for a given UE are sent only in
those special subframes. In this case the UE will never report
CQI and the eNB will use low MCS for this UE, impacting performances.

Another, related, problem is when there are several UEs. There again
one UE might always get its DCI0 in special subframes and thus never
report CQI. There again, performance issues.

This commit is an attempt to improve the situation.

It does two things.

1 - tag the UE as schedulable in the function UE_is_to_be_scheduled
    if the cqi_req_timer is expired

2 - use cqi_req_timer as a criterium when ordering UEs for UL scheduling

The value chosen for the expiration of the cqi_req_timer in
UE_is_to_be_scheduled is quite high (300) because as the code is
today we may overschedule the UE for short bursts until we receive
a CQI from the UE. [TODO: fix the code properly to avoid this behavior.]

Note: the fairRR scheduler has not been analyzed and this commit may
      not fix anything in case the fairRR scheduler is used.
      2a7ac81b