Accidental roaming can be eliminated simply by classifying cross-border as non-preferred networks and filtering roaming requests towards them from users whose previous connections originated from the home network. The actual roamer that crosses the border is eventually connected because he has either crossed the border or made a certain number of roaming requests. Customers who live near the border may be subject to additional requirements due to frequent accidental roaming cases, and additional requirements may apply to provide the best service.
Roaming prevention feature can be enabled/disabled per visited network. The system does not waste resources for genuine roaming cases into distant (non-neighboring) networks.
The Roaming Call Assistance (RCA) service intelligently monitors subscriber-initiated calls and corrects dialled shortcodes. -The system maintains a database of valid shortcodes and prefixes for the home network. When a given short code coincides with a valid short code in the visited network, it is possible to configure which one takes precedence over the other.
Border Roaming Prevention is triggered with the scenario on the here. After trigger, BRS determines whether starting-up prevention mechanism or not.
In the scenarios; ‘HLR’ stands for ‘Home Location Register’ and ‘MSC’ represents ‘Mobile Switching Center’. ‘GW’ stands for ‘Gateway’, ‘HPMN’ represents ‘Home Public Mobile Network’ and ‘NPMN’ represents ‘Near Public Mobile Network’.
Accidental roaming occurs when a mobile device accidentally registers to an external mobile network, even though the subscriber is geographically within the home network area. The combination of the following conditions causes unintended roaming
Subscribers are generally unaware of unintended roaming and are deeply dissatisfied with the high communication prices caused by accidental roaming. Also, inadvertent roaming can result in poor service (for example, being unable to make or receive calls), especially if the home and external networks are not interoperable.
BRS inspects all Location Update (LU) requests from neighbouring networks and decides if the LU request is accidental or genuine, depending on several criteria like the current cell id, if the current cell is a border cell, if there are multiple consecutive LU requests.