Dear experts, how can QRxlevmin be adjusted to disconnect users at the edge of the service area?
Any recommended values or best practices?
QRxlevmin should remain around -124 dBm, depending on the band. Reducing it further may lead to coverage holes.
qRxLevMin does not disconnect connected users, so it can’t kick an active edge user off. It is an idle/inactive-mode parameter that controls cell selection, reselection, and initial access through the S-criterion: Srxlev = measured RSRP minus qRxLevMin minus qRxLevMinOffset, and the UE only treats the cell as suitable to camp on or access when Srxlev is at least 0. It decides whether an idle UE can camp, reselect, or RACH into the cell, not whether a UE already in connected mode is released.
So raising qRxLevMin shrinks the idle footprint and blocks access below the threshold, which pushes idle UEs to reselect a neighbour instead of camping here. It does nothing to a user who is already connected at the edge.
If the real goal is to move connected edge users off this cell, that is a connected-mode function, not qRxLevMin: an A2 event (serving worse than threshold) triggering an inter-frequency or IRAT handover, or an RRC release with redirect to a better coverage layer. That is what actually relocates an active user.
On the value, I would not set a fixed dBm from a forum. Raising qRxLevMin without a better overlapping neighbour to catch those UEs creates coverage holes and access failures right at the edge, because you deny camping and access with nowhere for the UE to go. The correct value depends on your band, vendor, release, and above all your coverage overlap, so it comes from the neighbour layer you are steering onto, not a default number. Tell me the vendor, release, and what layer you want the edge users to land on, and whether they are idle or connected, and I will give the right mechanism and range for that case.