Mobility Robustness Optimization (MRO) Feature

Throughput can degrade because you delay the HO, mainly if traffic and PRB increases.

For low traffic I believe it will improve.

MRO is based on handovers too early or too late.

And RLFs counting based on the 2 counters above.

What is ping pong? :thinking:

Excessive handover between two cells.

1 Like

MRO is mainly control CIO offset for late and early HO.

There are counters in Huawei for late and early in neighbor relation, but mostly that counter is still not that clear to assume. You need to check ncell atttempts and timing advance of serving anf neighbor cells.

If your serving is more than 30 percent samples where in cell edge if its is more than 20 percent samples, then its case of overlapping or ping pong, its really a headache to see this much in reality.

30 percent samples with first tier nbrs.

Already checked.

And choose highest ping pong cell, but afraid if any KPI will be impacted.

Drop can in crease try in some cells mainly in low PRB case.

And traffic.

This is the point.

To minimize RLFs during HO, does MRO feature dynamically change the CIO after observing threshold (particular no. of RLFs) of too late or too early handovers? If yes, plz share call flow.