Handover stasis after successful handover about monster

[artuso0matteo]

Yes the value is set to 1ms only now simply cause I am debugging the feature which has been implemented fairly recently. we can then set it to a higher standard number. As for the stasis period afterwards, I agree with you that we probably won't need it, as the hysteresis timer basically achieves the same result. We mostly wanted to put all the TO-DOs and possible new features in the issue section of the repo and have a discussion about them

[mychele]

Hi Matteo,
where is the HO functionality implemented?
BTW, is your proposal standard? It could make sense, but maybe it's better to add some hysteresis in time and received power (e.g., as in the A* events for LTE HO).

[artuso0matteo]

HI! so the HO is implemented in the dev branch currently, we will merge the whole branch into master between this week and the next as we are doing some bugfixes. Right now, the HO check is started by the function "refreshUserAssociation.m" and then handled from there in the RLC folder.
We modelled the implementation by having an hysteresis parameter that controls in time an interval before switching to another eNodeB (handoverTimer in simulation.config) which is currently set to 1ms for debugging.

[mychele]

Thanks! Usually to avoid the ping-pong there is a higher value of this time interval (the possible values are actually ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120 from 36.331) and offsets in received power, but I never heard of this "wait time" after the HO. 2017-11-22 10:06 GMT+01:00 Matteo Artuso <[email protected]>:

…

HI! so the HO is implemented in the dev branch currently, we will merge the whole branch into master between this week and the next as we are doing some bugfixes. Right now, the HO check is started by the function "refreshUserAssociation.m" and then handled from there in the RLC folder. We modelled the implementation by having an hysteresis parameter that controls in time an interval before switching to another eNodeB (handoverTimer in simulation.config) which is currently set to 1ms for debugging. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG1b5UvlK9DCQ4T1yR9QSlRGu_1CfT7qks5s4-QHgaJpZM4QdSMS> .

-- Michele Polese Ph.D. Student Dept. of Information Engineering (DEI) - SIGNET Research Group University of Padova Via Gradenigo 6/B, 35131 Padova (Italy) email: [email protected] web: polese.io - mmwave.dei.unipd.it