Definition
Mobility Policy (Mobility Policy) refers to the strategic configuration of mobility-related parameters on the network side, such as handover, cell reselection (Cell Reselection), tracking area (TA) planning, and paging (Paging), aimed at optimizing network mobility performance, reducing signaling overhead, and achieving differentiated service assurance. Different service types (voice, data, IoT) can adopt differentiated policies; for example, IoT devices can be configured with longer DRX cycles and more relaxed TA update thresholds to reduce power consumption and signaling load.
Core Policy Elements
Handover Thresholds and Hysteresis
Thresholds and hysteresis values for events such as A3/A4/A5 (e.g., RSRP/RSRQ offsets) are used to control the timing of handover triggers and avoid ping-pong handovers. The greater the hysteresis, the more conservative the handover, resulting in less signaling but potentially sacrificing timeliness.
Reselection Priority
The priority for reselection of frequency bands/modes (e.g., LTE higher than 2G) and reselection thresholds (Srxlev, Squal) determines how idle terminals choose the serving cell. Higher priority frequency bands can be configured with lower access thresholds to guide terminals to preferentially reside in higher quality networks.
TA/TA List Planning
TA boundary planning affects the location update frequency. An overly large TA causes a wide paging range and more signaling; an overly small TA causes frequent TAUs. The TA List allows registration to multiple TAs, reducing updates when moving across TAs.
Paging Cycle and DRX
eDRX and Paging DRX cycle configuration determine the terminal's interval for listening to paging. IoT devices can adopt long DRX (e.g., 2.56s, 10.24s) or eDRX (e.g., 40.96s) to save power, at the expense of increased paging latency.
Typical Applications
Mobility strategies are widely applied in network optimization , handover optimization in high-speed scenarios like high-speed rail/subway, fine-tuned handover management , as well as power saving and low signaling configuration for IoT devices like NB-IoT and Cat.1.
The mobility behavior of SimtoLink IoT devices in operator networks is constrained by network-side policies. SimtoLink, during solution design, informs customers of the impacts on paging latency, location update frequency, etc., according to business characteristics (stationary/low mobility/in-vehicle), and assists customers in communicating with operators on configuration of power-saving strategies like eDRX and PSM, achieving a balance between power consumption and accessibility.
Threshold, Hysteresis, and Time-to-Trigger Have to Travel as a Set
A mobility policy is a group of decision rules that take effect together, not a single level threshold. In connected mode, an event such as A3 has to look at offset, hysteresis, and time-to-trigger at once. The neighbor has to be better than the serving cell by a set amount, and stay better for a set time, before a handover is allowed. Hysteresis blocks an instant flip caused by fast fading. Time-to-trigger blocks a vehicle that only briefly passes a strong cell. Shrink only the offset and leave the time-to-trigger alone, and the device hands back and forth between two cells. Signaling goes up, and the service gets worse.
Idle mode uses a different set of parameters. Reselection priority decides which carrier is looked at first. The S criterion decides whether the device may camp on that cell. A high-priority carrier can pull the device off a better low-band cell even when its level is only ordinary. The policy also has to set the tracking-area list and the paging cycle. Otherwise the device can sit on the right cell while its location scope and wake rhythm are still wrong. These three groups act on handover, camping, and reachability. Changing one group does not automatically correct another.
When to Push a Separate Profile for Each Speed
A stationary meter, a fixed camera on a factory floor, and a terminal on a highway vehicle cannot share one threshold set. A stationary device hardly needs aggressive handover. The threshold can be conservative, and the paging cycle follows the service delay. An in-vehicle device crosses many cells in a short time. Too long a time-to-trigger drops the call at the edge of the source cell. Too short a time-to-trigger ping-pongs in the overlap. High-speed rail and metro also have dedicated neighbors. The cells along the route should be chained, not left on the ordinary neighbor table of a public macro cell.
The policy can take effect only if the device really reports measurements and the network allows the matching feature. Once measurements are switched off to save power, even a carefully set handover threshold is never evaluated. An IoT SIM locked to a carrier or a cell throws reselection priority away. Across core-network pools, also confirm that the location update can finish on the new node. Otherwise handover signaling succeeds, tracking-area registration fails, and downlink then stops. Before a long idle stay, check the RRC state release timer so the device is not pulled back into connected mode by an overly aggressive policy just after it went idle.
Too Much Hysteresis Drags the Handover Past the Coverage Edge
A common mistake, made to cut signaling, is to push both hysteresis and time-to-trigger to the maximum. On a stretch with too little overlap, the device has not finished the handover when the source cell can no longer be decoded. The parameters look stable, and the drive test still drops. The opposite, setting hysteresis to zero at a junction with heavy high-rise reflection, hands over on every level jump, and the core sees a mass of handover cancellations. Another mistake is to tune only the RSRP threshold and ignore RSRQ. In a region of strong interference the pilot level still passes, the quality can no longer carry traffic, and a level-based policy never triggers a leave.
Reversed reselection priority is just as common. Set a crowded high band as the highest priority and every idle device camps on a carrier that has no capacity. Congestion shows up only after the connection is up. Count handover success, the ping-pong ratio, the carrier camped on after reselection, and the delay of one page, then change parameters. Accepting on “the signal got better” alone hides a bad policy.
After the parameters are sent, check the values that actually took effect on the device. Do not stop at the planned values in the network manager. A measurement event the device cannot support is ignored, and the threshold on the planning sheet never enters the decision. A locked-carrier test bypasses the whole reselection policy. Passing in the lab does not mean it still passes after the lock is removed. If one stretch of the route has too little overlap, relax the time-to-trigger on that stretch alone. Do not shrink hysteresis across the whole network. A network-wide reduction creates ping-pong in dense high-rise areas, and the local problem is still there.