ocn and ocp values in lte implementation

43 views
Skip to first unread message

Elen

unread,
Jun 24, 2026, 3:32:21 AMJun 24
to ns-3-users
Hello,
I'm looking on EVENT_A3 (lte-ue-rrc.h) handling in MeasurementReportTriggering and seems that ocn and ocp values are not being taken into calculation:
double ocn = 0.0; // Ocn, the cell specific offset of the neighbour cell
double mp; // Mp, the measurement result of the PCell
double ofp = measObjectEutra
.offsetFreq; // Ofp, the frequency specific offset of the primary frequency
double ocp = 0.0; // Ocp, the cell specific offset of the PCell
...
bool entryCond = mn + ofn + ocn - hys > mp + ofp + ocp + off;

And in
ApplyMeasConfig
there is this code:
NS_ASSERT_MSG(it->measObjectEutra.cellsToAddModList.empty(),
"cellsToAddModList not supported");


I'm working on case, when I would like to use ocn to implement load balancing (switch to another ENB, due to massive amount of UE that needs handover).
According to TS 36.331 the most correct way would be to use this offset for such situation.

Could you please suggest what should be the best way to approach this - add support of these options?
Create some callback with cellsToAddModList and sent to rrc?

Thanks in advance!

BR,
Jelena


Gabriel Ferreira

unread,
Jul 2, 2026, 5:09:37 PM (13 days ago) Jul 2
to ns-3-users
There are many ways you can implement it. We just implemented it into NR, so you may want to take a look. https://gitlab.com/cttc-lena/nr/-/commit/4735ccfc5930ad1cc554efb9fe41708e011a9960

Elen

unread,
Jul 4, 2026, 2:21:31 AM (12 days ago) Jul 4
to ns-3-users
Great, thank you, Gabriel!
I have implemented ocn calculation differently already,
 but I will compare with your NR solution and consider if I need to rewrite mine. 
 
BR, 
Jelena
Reply all
Reply to author
Forward
0 new messages