LTE Round Robin Algorithm in Uplink assignment with MCS=0

[Danilo A]

Hi Ns-3 Experts,

I am working on LTE Uplink scenario and I use Round-Robin scheduler algorithm as one of my benchmark.
I have seen that there is a problem in this algorithm, when the simulation starts it assigned RBs to UE even if the MCS=0.
Some of you experienced the same problem?
I saw that there is a patch for similar problem in downlink.

I attached the code I used as example. It is basically the same as lena-simple.cc
I tried changing the number of UEs attached to eNB and the problem remain.

Let me know if some of you had the same problem, in case there is no patch available I will open a bug.

Bye
Danilo

% time    cellId    IMSI    frame    sframe    RNTI    mcs    size    RbStart    RbLenght
0.026    1    1    3    7    1    0    49    0    15
0.027    1    1    3    8    1    0    49    0    15
0.028    1    1    3    9    1    0    49    0    15
0.029    1    1    3    10    1    0    49    0    15
0.03    1    1    4    1    1    0    49    0    15
0.031    1    1    4    2    1    0    49    0    15
0.032    1    1    4    3    1    0    49    0    15
0.033    1    1    4    4    1    28    1383    0    15
0.034    1    1    4    5    1    28    1383    0    15
0.035    1    1    4    6    1    28    1383    0    15

[Danilo A]

Up!

I tried to solve the problem.
I posted a review request at https://codereview.appspot.com/213460043/
For your convenience I also attached the new version of rr-ff-mac-scheduler.cc, UlMacStats.txt and the result of test.py on the round robin test suite.

Since in uplink each scheduler algorithm using the same code it is needed to change in all files.
If I receive any positive feedback I can change in the other files and provide a patch

Comments/questions/suggestions are very welcome

bye

Danilo

[Marco Miozzo]

Hi Danilo,

may I ask you to better explain the problem, in downlink the problem was related to CQI=0, if I remember correct, and it has been solved. I did not get why with MCS=0 a UE should not transmit, according to table 7.1.7.1-1 of 36.213 MCS 0 implies I_TBS 0 and a transport block size !=0, as reported in table 7.1.7.2.1-1.

Best regards,

marco.

--
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

[danilo abrignani]

Hi Marco,

you are right!

I just misreading the table 7.1.7.1-1 of 36.213.

So I will close the code review request

Thanks

Br,

Danilo

--
You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/HIze0UJxQ4g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.